Device, Method, and Graphical User Interface for Managing Icons in a User Interface Region

ABSTRACT

An electronic device displays a plurality of icons in a predefined area on the display, and detects a gesture that includes a contact on a touch-sensitive surface while a focus selector is over a respective icon, and subsequent movement of the contact across the touch-sensitive surface that corresponds to movement of the focus selector outside of the predefined area. In response to detecting the gesture, if the contact had a maximum intensity during the gesture that was below a respective intensity threshold, the device retains the respective icon in the predefined area after the gesture has ended. But if the contact reached an intensity during the gesture that was above the respective intensity threshold, the device moves the respective icon in accordance with the movement of the contact during the gesture and removes the respective icon from the predefined area after the gesture has ended.

RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.14/856,520, filed Sep. 16, 2015, which is a continuation of U.S.application Ser. No. 14/536,426, filed Nov. 7, 2014, now U.S. Pat. No.9,823,839, which is a continuation of PCT Patent Application Serial No.PCT/US2013/040058, filed on May 8, 2013, entitled “Device, Method, andGraphical User Interface for Displaying Additional Information inResponse to a User Contact,” which claims the benefit of and priority toU.S. Provisional Patent Application Ser. No. 61/778,171, filed on Mar.12, 2013, entitled “Device, Method, and Graphical User Interface forDisplaying Additional Information in Response to a User Contact;” U.S.Provisional Patent Application No. 61/747,278, filed Dec. 29, 2012,entitled “Device, Method, and Graphical User Interface for ManipulatingUser Interface Objects with Visual and/or Haptic Feedback;” and U.S.Provisional Patent Application No. 61/688,227, filed May 9, 2012,entitled “Device, Method, and Graphical User Interface for ManipulatingUser Interface Objects with Visual and/or Haptic Feedback,” whichapplications are incorporated by reference herein in their entireties.

This application is also related to the following: U.S. ProvisionalPatent Application Ser. No. 61/778,092, filed on Mar. 12, 2013, entitled“Device, Method, and Graphical User Interface for Selecting Objectwithin a Group of Objects;” U.S. Provisional Patent Application Ser. No.61/778,125, filed on Mar. 12, 2013, entitled “Device, Method, andGraphical User Interface for Navigating User Interface Hierarchies;”U.S. Provisional Patent Application Ser. No. 61/778,156, filed on Mar.12, 2013, entitled “Device, Method, and Graphical User Interface forManipulating Framed Graphical Objects;” U.S. Provisional PatentApplication Ser. No. 61/778,179, filed on Mar. 12, 2013, entitled“Device, Method, and Graphical User Interface for Scrolling NestedRegions;” U.S. Provisional Patent Application Ser. No. 61/778,191, filedon Mar. 12, 2013, entitled “Device, Method, and Graphical User Interfacefor Displaying User Interface Objects Corresponding to an Application;”U.S. Provisional Patent Application Ser. No. 61/778,211, filed on Mar.12, 2013, entitled “Device, Method, and Graphical User Interface forFacilitating User Interaction with Controls in a User Interface;” U.S.Provisional Patent Application Ser. No. 61/778,239, filed on Mar. 12,2013, entitled “Device, Method, and Graphical User Interface forForgoing Generation of Tactile Output for a Multi-Contact Gesture;” U.S.Provisional Patent Application Ser. No. 61/778,284, filed on Mar. 12,2013, entitled “Device, Method, and Graphical User Interface forProviding Tactile Feedback for Operations Performed in a UserInterface;” U.S. Provisional Patent Application Ser. No. 61/778,287,filed on Mar. 12, 2013, entitled “Device, Method, and Graphical UserInterface for Providing Feedback for Changing Activation States of aUser Interface Object;” U.S. Provisional Patent Application Ser. No.61/778,363, filed on Mar. 12, 2013, entitled “Device, Method, andGraphical User Interface for Transitioning between Touch Input toDisplay Output Relationships;” U.S. Provisional Patent Application Ser.No. 61/778,367, filed on Mar. 12, 2013, entitled “Device, Method, andGraphical User Interface for Moving a User Interface Object Based on anIntensity of a Press Input;” U.S. Provisional Patent Application Ser.No. 61/778,265, filed on Mar. 12, 2013, entitled “Device, Method, andGraphical User Interface for Transitioning between Display States inResponse to a Gesture;” U.S. Provisional Patent Application Ser. No.61/778,373, filed on Mar. 12, 2013, entitled “Device, Method, andGraphical User Interface for Managing Activation of a Control Based onContact Intensity;” U.S. Provisional Patent Application Ser. No.61/778,412, filed on Mar. 13, 2013, entitled “Device, Method, andGraphical User Interface for Displaying Content Associated with aCorresponding Affordance;” U.S. Provisional Patent Application Ser. No.61/778,413, filed on Mar. 13, 2013, entitled “Device, Method, andGraphical User Interface for Selecting User Interface Objects;” U.S.Provisional Patent Application Ser. No. 61/778,414, filed on Mar. 13,2013, entitled “Device, Method, and Graphical User Interface for Movingand Dropping a User Interface Object;” U.S. Provisional PatentApplication Ser. No. 61/778,416, filed on Mar. 13, 2013, entitled“Device, Method, and Graphical User Interface for Determining Whether toScroll or Select Content;” and U.S. Provisional Patent Application Ser.No. 61/778,418, filed on Mar. 13, 2013, entitled “Device, Method, andGraphical User Interface for Switching between User Interfaces,” whichare incorporated herein by reference in their entireties.

This application is also related to the following: U.S. ProvisionalPatent Application Ser. No. 61/645,033, filed on May 9, 2012, entitled“Adaptive Haptic Feedback for Electronic Devices;” U.S. ProvisionalPatent Application Ser. No. 61/665,603, filed on Jun. 28, 2012, entitled“Adaptive Haptic Feedback for Electronic Devices;” and U.S. ProvisionalPatent Application Ser. No. 61/681,098, filed on Aug. 8, 2012, entitled“Adaptive Haptic Feedback for Electronic Devices,” which areincorporated herein by reference in their entireties.

TECHNICAL FIELD

This relates generally to electronic devices with touch-sensitivesurfaces, including but not limited to electronic devices withtouch-sensitive surfaces that detect inputs for manipulating userinterfaces.

BACKGROUND

The use of touch-sensitive surfaces as input devices for computers andother electronic computing devices has increased significantly in recentyears. Exemplary touch-sensitive surfaces include touch pads and touchscreen displays. Such surfaces are widely used to manipulate userinterface objects on a display.

Exemplary manipulations include adjusting the position and/or size ofone or more user interface objects or activating buttons or openingfiles/applications represented by user interface objects, as well asassociating metadata with one or more user interface objects orotherwise manipulating user interfaces. Exemplary user interface objectsinclude digital images, video, text, icons, control elements such asbuttons and other graphics. A user will, in some circumstances, need toperform such manipulations on user interface objects in a filemanagement program (e.g., Finder from Apple Inc. of Cupertino, Calif.),an image management application (e.g., Aperture or iPhoto from AppleInc. of Cupertino, Calif.), a digital content (e.g., videos and music)management application (e.g., iTunes from Apple Inc. of Cupertino,Calif.), a drawing application, a presentation application (e.g.,Keynote from Apple Inc. of Cupertino, Calif.), a word processingapplication (e.g., Pages from Apple Inc. of Cupertino, Calif.), awebsite creation application (e.g., iWeb from Apple Inc. of Cupertino,Calif.), a disk authoring application (e.g., iDVD from Apple Inc. ofCupertino, Calif.), or a spreadsheet application (e.g., Numbers fromApple Inc. of Cupertino, Calif.).

But existing methods for performing these manipulations are cumbersomeand inefficient. In addition, existing methods take longer thannecessary, thereby wasting energy. This latter consideration isparticularly important in battery-operated devices.

SUMMARY

Accordingly, there is a need for electronic devices with faster, moreefficient methods and interfaces for manipulating user interfaces. Suchmethods and interfaces optionally complement or replace conventionalmethods for manipulating user interfaces. Such methods and interfacesreduce the cognitive burden on a user and produce a more efficienthuman-machine interface. For battery-operated devices, such methods andinterfaces conserve power and increase the time between battery charges.

The above deficiencies and other problems associated with userinterfaces for electronic devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device has a touchpad. In someembodiments, the device has a touch-sensitive display (also known as a“touch screen” or “touch screen display”). In some embodiments, thedevice has a graphical user interface (GUI), one or more processors,memory and one or more modules, programs or sets of instructions storedin the memory for performing multiple functions. In some embodiments,the user interacts with the GUI primarily through finger contacts andgestures on the touch-sensitive surface. In some embodiments, thefunctions optionally include image editing, drawing, presenting, wordprocessing, website creating, disk authoring, spreadsheet making, gameplaying, telephoning, video conferencing, e-mailing, instant messaging,workout support, digital photographing, digital videoing, web browsing,digital music playing, and/or digital video playing. Executableinstructions for performing these functions are, optionally, included ina non-transitory computer readable storage medium or other computerprogram product configured for execution by one or more processors.

There is a need for electronic devices with faster, more efficientmethods and interfaces for performing user interface operations on anelectronic device with a track pad or touch screen. Examples of suchoperations including scrolling through a list of items or deleting anitem in the list. Such methods and interfaces may complement or replaceconventional methods for performing user interface operations. Suchmethods and interfaces reduce the cognitive burden on a user and producea more efficient human-machine interface. For battery-operated devices,such methods and interfaces conserve power and increase the time betweenbattery charges.

In accordance with some embodiments, a method is performed at anelectronic device with a display, a touch-sensitive surface and one ormore sensors to detect intensity of contacts with the touch-sensitivesurface. The method includes: displaying a user interface on the displayand detecting a gesture by a user on the touch-sensitive surface thatincludes a contact that corresponds to a focus selector at a respectivelocation in the user interface, where the gesture is associated with arespective operation. The method further includes, in response todetecting the gesture, in accordance with a determination that thecontact has a maximum intensity below a first intensity threshold,requesting confirmation that the user wants the device to perform therespective operation. The method further includes, in accordance with adetermination that the maximum intensity of the contact is above thefirst intensity threshold, performing the respective operation withoutrequesting confirmation that the user wants the device to perform therespective operation.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display a user interface on the display unit;a touch-sensitive surface unit configured to detect a gesture by a useron the touch-sensitive surface unit that includes a contact thatcorresponds to a focus selector at a respective location in the userinterface, wherein the gesture is associated with a respectiveoperation; and a processing unit coupled to the display unit and thetouch-sensitive surface unit. The processing unit is configured to: inresponse to detecting the gesture: in accordance with a determinationthat the contact has a maximum intensity below a first intensitythreshold, request confirmation that the user wants the device toperform the respective operation; and in accordance with a determinationthat the maximum intensity of the contact is above the first intensitythreshold, perform the respective operation without requestingconfirmation that the user wants the device to perform the respectiveoperation.

Thus, electronic devices with displays, touch-sensitive surfaces and oneor more sensors to detect intensity of contacts with the touch-sensitivesurface are provided with faster, more efficient methods and interfacesfor performing user interface operations, thereby increasing theeffectiveness, efficiency, and user satisfaction with such devices. Suchmethods and interfaces may complement or replace conventional methodsfor performing user interface operations.

There is a need for electronic devices with faster, more efficientmethods and interfaces for displaying additional (e.g., initiallyundisplayed) information when a user contact is detected while a focusselector that corresponds to the contact is at a location on a displaythat is associated with the additional information. Such methods andinterfaces may complement or replace conventional methods for displayingsuch additional information. Such methods and interfaces reduce thecognitive burden on a user and produce a more efficient human-machineinterface. For battery-operated devices, such methods and interfacesconserve power and increase the time between battery charges.

In accordance with some embodiments, a method is performed at anelectronic device with a display, a touch-sensitive surface and one ormore sensors to detect intensity of contacts with the touch-sensitivesurface. The method includes detecting a contact on the touch-sensitivesurface while a focus selector corresponding to the contact is at arespective location on the display that is associated with additionalinformation that is not initially displayed on the display. The methodfurther includes, while the focus selector is at the respectivelocation: in accordance with a determination that the contact has anintensity above a respective intensity threshold before a predefineddelay time has elapsed with the focus selector at the respectivelocation, displaying the additional information associated with therespective location without waiting until the predefined delay time haselapsed; and in accordance with a determination that the contact has anintensity below the respective intensity threshold, waiting until thepredefined delay time has elapsed while the focus selector is at therespective location to display the additional information associatedwith the respective location.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display additional information associatedwith a respective location; a touch sensitive surface unit configured toreceive a contact on the touch-sensitive surface unit; one or moresensor units configured to detect intensity of contacts with thetouch-sensitive surface unit; and a processing unit coupled to thedisplay unit, the touch-sensitive surface unit, and the sensor units.The processing unit is configured to: detect a contact on thetouch-sensitive surface unit while a focus selector corresponding to thecontact is at a respective location on the display unit that isassociated with additional information that is not initially displayedon the display unit; and while the focus selector is at the respectivelocation: in accordance with a determination that the contact has anintensity above a respective intensity threshold before a predefineddelay time has elapsed with the focus selector at the respectivelocation, enable display of the additional information associated withthe respective location without waiting until the predefined delay timehas elapsed; and in accordance with a determination that the contact hasan intensity below the respective intensity threshold, wait until thepredefined delay time has elapsed while the focus selector is at therespective location to enable display of the additional informationassociated with the respective location.

Thus, electronic devices with displays, touch-sensitive surfaces and oneor more sensors to detect intensity of contacts with the touch-sensitivesurface are provided with faster, more efficient methods and interfacesfor displaying additional (e.g., initially undisplayed) information whena contact is detected, thereby increasing the effectiveness, efficiency,and user satisfaction with such devices. Such methods and interfaces maycomplement or replace conventional methods for displaying additional(e.g., initially undisplayed) information when a contact is detected.

There is a need for electronic devices with faster, more efficientmethods and interfaces for removing an icon from a predefined area. Suchmethods and interfaces may complement or replace conventional methodsfor removing an icon from a predefined area. Such methods and interfacesreduce the cognitive burden on a user and produce a more efficienthuman-machine interface. For battery-operated devices, such methods andinterfaces conserve power and increase the time between battery charges.

In accordance with some embodiments, a method is performed at anelectronic device with a display, a touch-sensitive surface, and one ormore sensors to detect intensity of contacts with the touch-sensitivesurface. The method includes: displaying a plurality of icons in apredefined area on the display, where the plurality of icons include arespective icon; detecting a gesture that includes: a contact on thetouch-sensitive surface while a focus selector is over the respectiveicon and subsequent movement of the contact across the touch-sensitivesurface that corresponds to movement of the focus selector outside ofthe predefined area; and in response to detecting the gesture: inaccordance with a determination that the contact had a maximum intensityduring the gesture that was below a respective intensity threshold,displaying an indication that the gesture is being performed during thegesture and retaining the respective icon in the predefined area afterthe gesture has ended; and in accordance with a determination that thecontact reached an intensity during the gesture that was above therespective intensity threshold, moving the respective icon in accordancewith the movement of the contact during the gesture and removing therespective icon from the predefined area after the gesture has ended.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display a plurality of icons in a predefinedarea on the display unit, wherein the plurality of icons include arespective icon; a touch-sensitive surface unit configured to receivegestures; one or more sensor units configured to detect intensity ofcontacts with the touch-sensitive surface unit; and a processing unitcoupled to the display unit, the touch-sensitive surface unit, and thesensor units. The processing unit is configured to: detect a gesturethat includes a contact on the touch-sensitive surface unit while afocus selector is over the respective icon and subsequent movement ofthe contact across the touch-sensitive surface unit that corresponds tomovement of the focus selector outside of the predefined area, and inresponse to detecting the gesture: in accordance with a determinationthat the contact had a maximum intensity during the gesture that wasbelow a respective intensity threshold, enable display of an indicationthat the gesture is being performed during the gesture and retain therespective icon in the predefined area after the gesture has ended; andin accordance with a determination that the contact reached an intensityduring the gesture that was above the respective intensity threshold,move the respective icon in accordance with the movement of the contactduring the gesture and remove the respective icon from the predefinedarea after the gesture has ended.

Thus, electronic devices with displays, touch-sensitive surfaces, andone or more sensors to detect intensity of contacts with thetouch-sensitive surface are provided with faster, more efficient methodsand interfaces for removing an icon from a predefined area, therebyincreasing the effectiveness, efficiency, and user satisfaction withsuch devices. Such methods and interfaces may complement or replaceconventional methods for removing an icon from a predefined area.

There is a need for electronic devices with faster, more efficientmethods and interfaces for displaying content layers. Such methods andinterfaces may complement or replace conventional methods for displayingcontent layers. Such methods and interfaces reduce the cognitive burdenon a user and produce a more efficient human-machine interface. Forbattery-operated devices, such methods and interfaces conserve power andincrease the time between battery charges.

In accordance with some embodiments, a method is performed at anelectronic device with a display, a touch-sensitive surface and one ormore sensors to detect intensity of contacts with the touch-sensitivesurface. The method includes: displaying, on the display, first content,where portions of the first content are correlated with correspondingportions of second content that are not displayed on the display; whilea focus selector is over a first portion of the first content, detectingan increase in intensity of a contact on the touch-sensitive surfaceabove a respective intensity threshold; and in response to detecting theincrease in intensity of the contact on the touch-sensitive surfaceabove the respective intensity threshold: ceasing to display the firstportion of the first content, and displaying a first portion of thesecond content that corresponds to the first portion of the firstcontent.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display, on the display unit, first content,where portions of the first content are correlated with correspondingportions of second content that are not displayed on the display unit; atouch-sensitive surface unit configured to receive contacts; one or moresensors configured to detect intensity of contacts with thetouch-sensitive surface unit; and a processing unit coupled to thedisplay unit, the touch-sensitive surface unit, and the sensors. Theprocessing unit is configured to: while a focus selector is over a firstportion of the first content, detect an increase in intensity of acontact on the touch-sensitive surface unit above a respective intensitythreshold; and in response to detecting the increase in intensity of thecontact on the touch-sensitive surface unit above the respectiveintensity threshold: cease to display the first portion of the firstcontent, and enable display of a first portion of the second contentthat corresponds to the first portion of the first content.

Thus, electronic devices with displays, touch-sensitive surfaces and oneor more sensors to detect intensity of contacts with the touch-sensitivesurface are provided with faster, more efficient methods and interfacesfor displaying content layers, thereby increasing the effectiveness,efficiency, and user satisfaction with such devices. Such methods andinterfaces may complement or replace conventional methods for displayingcontent layers.

There is a need for electronic devices with faster, more efficientmethods and interfaces for navigating between user interfaces (forexample between an inbox view and a conversation view in an email clientapplication) by using user inputs, such as inputs on a track pad ortouch screen, or inputs from a touch-sensitive surface. Such methods andinterfaces may complement or replace conventional methods for navigatingbetween user interfaces. Such methods and interfaces reduce thecognitive burden on a user and produce a more efficient human-machineinterface. For battery-operated devices, such methods and interfacesconserve power and increase the time between battery charges.

In accordance with some embodiments, a method is performed at anelectronic device with a display, a touch-sensitive surface and one ormore sensors to detect intensity of contacts with the touch-sensitivesurface. The method includes: displaying a first user interface on thedisplay. The method further includes, while a focus selector is over afirst representation of an object in the first user interface, detectinga first gesture on the touch-sensitive surface that includes a firstcontact with a maximum intensity during the first gesture above arespective intensity threshold. The method further includes, in responseto detecting the first gesture, replacing the first user interface witha second user interface that includes a second representation of theobject. The method further includes, while the focus selector is overthe second representation of the object in the second user interface,detecting a second gesture on the touch-sensitive surface that includesa second contact with a maximum intensity during the second gestureabove the respective intensity threshold. The method further includes,in response to detecting the second gesture, replacing the second userinterface with the first user interface.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display a first user interface that includesa first representation of an object and a second user interface thatincludes a second representation of the object; a touch-sensitivesurface unit configured to detect, while a focus selector is over thefirst representation of the object in the first user interface, a firstgesture on the touch-sensitive surface unit that includes a firstcontact with a maximum intensity during the first gesture above arespective intensity threshold, and to detect, while the focus selectoris over the second representation of the object in the second userinterface, a second gesture on the touch-sensitive surface unit thatincludes a second contact with a maximum intensity during the secondgesture above the respective intensity threshold; and a processing unitcoupled to the display unit and the touch-sensitive surface unit. Theprocessing unit is configured to: in response to detecting the firstgesture, replace the first user interface with the second userinterface; and in response to detecting the second gesture, replace thesecond user interface with the first user interface.

Thus, electronic devices with displays, touch-sensitive surfaces and oneor more sensors to detect intensity of contacts with the touch-sensitivesurface are provided with faster, more efficient methods and interfacesfor navigating between displayed user interfaces, thereby increasing theeffectiveness, efficiency, and user satisfaction with such devices. Suchmethods and interfaces may complement or replace conventional methodsfor navigating between displayed user interfaces.

In accordance with some embodiments, an electronic device includes adisplay, a touch-sensitive surface, optionally one or more sensors todetect intensity of contacts with the touch-sensitive surface, one ormore processors, memory, and one or more programs; the one or moreprograms are stored in the memory and configured to be executed by theone or more processors and the one or more programs include instructionsfor performing the operations of any of the methods referred to in thefifth paragraph of the Description of Embodiments. In accordance withsome embodiments, a graphical user interface on an electronic devicewith a display, a touch-sensitive surface, optionally one or moresensors to detect intensity of contacts with the touch-sensitivesurface, a memory, and one or more processors to execute one or moreprograms stored in the memory includes one or more of the elementsdisplayed in any of the methods referred to in the fifth paragraph ofthe Description of Embodiments, which are updated in response to inputs,as described in any of the methods referred to the fifth paragraph ofthe Description of Embodiments. In accordance with some embodiments, acomputer readable storage medium has stored therein instructions whichwhen executed by an electronic device with a display, a touch-sensitivesurface, and optionally one or more sensors to detect intensity ofcontacts with the touch-sensitive surface, cause the device to performthe operations of any of the methods referred to in the fifth paragraphof the Description of Embodiments. In accordance with some embodiments,an electronic device includes: a display, a touch-sensitive surface, andoptionally one or more sensors to detect intensity of contacts with thetouch-sensitive surface; and means for performing the operations of anyof the methods referred to in the fifth paragraph of the Description ofEmbodiments. In accordance with some embodiments, an informationprocessing apparatus, for use in an electronic device with a display anda touch-sensitive surface, optionally one or more sensors to detectintensity of contacts with the touch-sensitive surface, includes meansfor performing the operations of any of the methods referred to in thefifth paragraph of the Description of Embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIGS. 5A-5I illustrate exemplary user interfaces for performing userinterface operations in accordance with some embodiments.

FIGS. 6A-6B are flow diagrams illustrating a method of performing userinterface operations in accordance with some embodiments.

FIG. 7 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIGS. 8A-8N illustrate exemplary user interfaces for displayingadditional information associated with a location on a display based oncontact intensity (e.g., pressure) and contact timing (e.g., duration)in accordance with some embodiments.

FIGS. 9A-9B are flow diagrams illustrating a method of displayingadditional information associated with a location on a display based oncontact intensity (e.g., pressure) and contact timing (e.g., duration)in accordance with some embodiments.

FIG. 10 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIGS. 11A-11U illustrate exemplary user interfaces for removing an iconfrom a predefined area in accordance with some embodiments.

FIGS. 12A-12B are flow diagrams illustrating a method of removing anicon from a predefined area in accordance with some embodiments.

FIG. 13 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIGS. 14A-14L illustrate exemplary user interfaces for displayingcontent layers in accordance with some embodiments.

FIGS. 15A-15C are flow diagrams illustrating a method of displayingcontent layers in accordance with some embodiments.

FIG. 16 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIGS. 17A-17H illustrate exemplary user interfaces for navigatingbetween displayed user interfaces in accordance with some embodiments.

FIGS. 18A-18C are flow diagrams illustrating a method of navigatingbetween displayed user interfaces in accordance with some embodiments.

FIG. 19 is a functional block diagram of an electronic device inaccordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The methods, devices and GUIs described herein provide visual and/orhaptic feedback that makes manipulation of user interface objects moreefficient and intuitive for a user. For example, in a system where theclicking action of a trackpad is decoupled from the contact intensity(e.g., contact force, contact pressure, or a substitute therefore) thatis needed to reach an activation threshold, the device can generatedifferent tactile outputs (e.g., “different clicks”) for differentactivation events (e.g., so that clicks that accomplish a particularresult are differentiated from clicks that do not produce any result orthat accomplish a different result from the particular result).Additionally, tactile outputs can be generated in response to otherevents that are not related to increasing intensity of a contact, suchas generating a tactile output (e.g., a “detent”) when a user interfaceobject is moved to a particular position, boundary or orientation, orwhen an event occurs at the device.

Additionally, in a system where a trackpad or touch-screen display issensitive to a range of contact intensity that includes more than one ortwo specific intensity values (e.g., more than a simple on/off, binaryintensity determination), the user interface can provide responses(e.g., visual or tactile cues) that are indicative of the intensity ofthe contact within the range. In some implementations, apre-activation-threshold response and/or a post-activation-thresholdresponse to an input are displayed as continuous animations. As oneexample of such a response, a preview of an operation is displayed inresponse to detecting an increase in contact intensity that is stillbelow an activation threshold for performing the operation. As anotherexample of such a response, an animation associated with an operationcontinues even after the activation threshold for the operation has beenreached. Both of these examples provide a user with a continuousresponse to the force or pressure of a user's contact, which provides auser with visual and/or haptic feedback that is richer and moreintuitive. More specifically, such continuous force responses give theuser the experience of being able to press lightly to preview anoperation and/or press deeply to push “past” or “through” a predefineduser interface state corresponding to the operation.

Additionally, for a device with a touch-sensitive surface that issensitive to a range of contact intensity, multiple contact intensitythresholds can be monitored by the device and different functions can bemapped to different contact intensity thresholds. This serves toincrease the available “gesture space” providing easy access to advancedfeatures for users who know that increasing the intensity of a contactat or beyond a second “deep press” intensity threshold will cause thedevice to perform a different operation from an operation that would beperformed if the intensity of the contact is between a first“activation” intensity threshold and the second “deep press” intensitythreshold. An advantage of assigning additional functionality to asecond “deep press” intensity threshold while maintaining familiarfunctionality at a first “activation” intensity threshold is thatinexperienced users who are, in some circumstances, confused by theadditional functionality can use the familiar functionality by justapplying an intensity up to the first “activation” intensity threshold,whereas more experienced users can take advantage of the additionalfunctionality by applying an intensity at the second “deep press”intensity threshold.

Additionally, for a device with a touch-sensitive surface that issensitive to a range of contact intensity, the device can provideadditional functionality by allowing users to perform complex operationswith a single continuous contact. For example, when selecting a group ofobjects, a user can move a continuous contact around the touch-sensitivesurface and can press while dragging (e.g., applying an intensitygreater than a “deep press” intensity threshold) to add additionalelements to a selection. In this way, a user can intuitively interactwith a user interface where pressing harder with a contact causesobjects in the user interface to be “stickier.”

A number of different approaches to providing an intuitive userinterface on a device where a clicking action is decoupled from theforce that is needed to reach an activation threshold and/or the deviceis sensitive to a wide range of contact intensities are described below.Using one or more of these approaches (optionally in conjunction witheach other) helps to provide a user interface that intuitively providesusers with additional information and functionality, thereby reducingthe user's cognitive burden and improving the human-machine interface.Such improvements in the human-machine interface enable users to use thedevice faster and more efficiently. For battery-operated devices, theseimprovements conserve power and increase the time between batterycharges. For ease of explanation, systems, methods and user interfacesfor including illustrative examples of some of these approaches aredescribed below, as follows:

-   -   Many electronic devices have user interfaces for performing user        interface operations, such as viewing user interface objects        (photos, email message, etc.) and deleting user interface        objects. In some circumstances, destructive operations are        performed (e.g., deleting an email), and the devices require an        extra input (e.g., a confirmation input) before performing these        operations. However, providing a sequence of inputs can be        confusing and time consuming for a user. In the embodiments        described below, a device determines whether or not to perform a        particular destructive operation based on the intensity of a        contact corresponding to a request to perform a particular        destructive operation, thereby providing a more intuitive and        efficient user interface for performing destructive operations.        In particular, FIGS. 5A-5I illustrate exemplary user interfaces        for performing user interface operations. FIGS. 6A-6B are flow        diagrams illustrating a method of performing user interface        operations. The user interfaces in FIGS. 5A-5I are used to        illustrate the processes in FIGS. 6A-6B.    -   Many electronic devices have graphical user interfaces that        include user interface objects. In some instances, additional        (e.g., hidden) information associated with user interface        objects is displayed at the request of a user. Some devices        display such additional information after, for example,        detecting a focus selector over the user interface object for an        extended period of time. However, such methods are time        consuming and frustrating to users. The embodiments described        below provide improved methods of displaying additional        information based on the intensity (e.g., pressure) of a contact        on the touch-sensitive surface, thereby providing a more        convenient and efficient user interface for displaying        additional information. In particular, FIGS. 8A-8N illustrate        exemplary user interfaces for displaying additional information        associated with a location (for example, corresponding to a user        interface object) on a display based on contact intensity (e.g.,        pressure) and contact timing (e.g., duration). FIGS. 9A-9B are        flow diagrams illustrating a method of displaying additional        information based on contact intensity (e.g., pressure) and        contact timing (e.g., duration). The user interfaces in FIGS.        8A-8N are used to illustrate the processes in FIGS. 9A-9B.    -   Many electronic devices have graphical user interfaces that        include an application dock or launch bar. In some situations a        user is enabled to remove or rearrange icons in an application        dock or launch bar. However, when the icons are accidentally        removed or rearranged the user can become frustrated or        confused. Additionally, adding back accidentally removed icons        and undoing an accidental rearranging operation is frustrating        and inefficient for users. The embodiments described below        provide improved methods for removing unwanted icons from a        predefined area, such as a launchbar where the device determines        whether or not to remove or rearrange icons in the predefined        area in accordance with an intensity of a contact, thereby        providing a more intuitive and efficient user interface that is        less frustrating for users. In particular, FIGS. 11A-11U        illustrate exemplary user interfaces for removing an icon from a        predefined area. FIGS. 12A-12B are flow diagrams illustrating a        method of removing an icon from a predefined area. The user        interfaces in FIGS. 11A-11U are used to illustrate the processes        in FIGS. 12A-12B.    -   Many electronic devices include applications or user interfaces        where different corresponding content, such as layers of        content, can be displayed. It is easy for a user to lose their        place within the layers or become confused as to how to navigate        through the layers. The embodiments described below provide an        efficient and intuitive user interface for navigating and        displaying layers of content by determining whether and,        optionally, how much of an underlying layer to reveal based on        the intensity of a contact on a touch-sensitive surface. In        particular, FIGS. 14A-14L illustrate exemplary user interfaces        for displaying content layers. FIGS. 15A-15C are flow diagrams        illustrating a method of displaying content layers. The user        interfaces in FIGS. 14A-14L are used to illustrate the processes        in FIGS. 15A-15C.    -   Many electronic devices include user interfaces that include        different representations of a same object (e.g., content such        as an email or photo). Some methods for navigating between user        interfaces on a device with a touch-sensitive surface typically        require a user to locate an affordance (e.g., a key or a        “button”). Such methods, however, are problematic because they        are prone to inaccuracies (e.g., accidental selection of the        affordance, accidental selection of a different key when        intending to select the affordance). Such methods also increase        the cognitive burden on the user by requiring additional        independent gestures. The embodiments described below provide a        convenient and intuitive method for navigating between user        interfaces corresponding to different representations of an        object using similar gestures performed with a contact while a        focus selector is over a representation of the object. In        particular, FIGS. 17A-17H illustrate exemplary user interfaces        for navigating between displayed user interfaces. FIGS. 18A-18C        are flow diagrams illustrating a method of navigating between        displayed user interfaces. The user interfaces in FIGS. 17A-17H        are used to illustrate the processes in FIGS. 18A-18C.

Exemplary Devices

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the various described embodiments. However,it will be apparent to one of ordinary skill in the art that the variousdescribed embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components,circuits, and networks have not been described in detail so as not tounnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first contactcould be termed a second contact, and, similarly, a second contact couldbe termed a first contact, without departing from the scope of thevarious described embodiments. The first contact and the second contactare both contacts, but they are not the same contact.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting,”depending on the context. Similarly, the phrase “if it is determined” or“if [a stated condition or event] is detected” is, optionally, construedto mean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touch pads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touch pad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive displays 112 inaccordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience, and is sometimesknown as or called a touch-sensitive display system. Device 100 includesmemory 102 (which optionally includes one or more computer readablestorage mediums), memory controller 122, one or more processing units(CPU's) 120, peripherals interface 118, RF circuitry 108, audiocircuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem106, other input or control devices 116, and external port 124. Device100 optionally includes one or more optical sensors 164. Device 100optionally includes one or more intensity sensors 165 for detectingintensity of contacts on device 100 (e.g., a touch-sensitive surfacesuch as touch-sensitive display system 112 of device 100). Device 100optionally includes one or more tactile output generators 167 forgenerating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on the touchsensitive surface, or to a substitute (proxy) for the force or pressureof a contact on the touch sensitive surface. The intensity of a contacthas a range of values that includes at least four distinct values andmore typically includes hundreds of distinct values (e.g., at least256). Intensity of a contact is, optionally, determined (or measured)using various approaches and various sensors or combinations of sensors.For example, one or more force sensors underneath or adjacent to thetouch-sensitive surface are, optionally, used to measure force atvarious points on the touch-sensitive surface. In some implementations,force measurements from multiple force sensors are combined (e.g., aweighted average) to determine an estimated force of a contact.Similarly, a pressure-sensitive tip of a stylus is, optionally, used todetermine a pressure of the stylus on the touch-sensitive surface.Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure and the estimated force or pressure isused to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/or applicationspecific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Access to memory 102 by othercomponents of device 100, such as CPU 120 and the peripherals interface118, is, optionally, controlled by memory controller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU 120, and memorycontroller 122 are, optionally, implemented on a single chip, such aschip 104. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over InternetProtocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet messageaccess protocol (IMAP) and/or post office protocol (POP)), instantmessaging (e.g., extensible messaging and presence protocol (XMPP),Session Initiation Protocol for Instant Messaging and PresenceLeveraging Extensions (SIMPLE), Instant Messaging and Presence Service(IMPS)), and/or Short Message Service (SMS), or any other suitablecommunication protocol, including communication protocols not yetdeveloped as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161 and one or more input controllers 160 forother input or control devices. The one or more input controllers 160receive/send electrical signals from/to other input or control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, infrared port, USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor or set of sensorsthat accepts input from the user based on haptic and/or tactile contact.Touch screen 112 and display controller 156 (along with any associatedmodules and/or sets of instructions in memory 102) detect contact (andany movement or breaking of the contact) on touch screen 112 andconverts the detected contact into interaction with user-interfaceobjects (e.g., one or more soft keys, icons, web pages or images) thatare displayed on touch screen 112. In an exemplary embodiment, a pointof contact between touch screen 112 and the user corresponds to a fingerof the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch screen 112 or anextension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor 164 optionally capturesstill images or video. In some embodiments, an optical sensor is locatedon the back of device 100, opposite touch screen display 112 on thefront of the device, so that the touch screen display is enabled for useas a viewfinder for still and/or video image acquisition. In someembodiments, another optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained forvideoconferencing while the user views the other video conferenceparticipants on the touch screen display.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112 which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is coupled to input controller 160 inI/O subsystem 106. In some embodiments, the proximity sensor turns offand disables touch screen 112 when the multifunction device is placednear the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112 which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. In some embodiments, information isdisplayed on the touch screen display in a portrait view or a landscapeview based on an analysis of data received from the one or moreaccelerometers. Device 100 optionally includes, in addition toaccelerometer(s) 168, a magnetometer (not shown) and a GPS (or GLONASSor other global navigation system) receiver (not shown) for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments memory 102 stores device/globalinternal state 157, as shown in FIGS. 1A and 3. Device/global internalstate 157 includes one or more of: active application state, indicatingwhich applications, if any, are currently active; display state,indicating what applications, views or other information occupy variousregions of touch screen display 112; sensor state, including informationobtained from the device's various sensors and input control devices116; and location information concerning the device's location and/orattitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, oran embedded operating system such as VxWorks) includes various softwarecomponents and/or drivers for controlling and managing general systemtasks (e.g., memory management, storage device control, powermanagement, etc.) and facilitates communication between various hardwareand software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used on iPod (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and other touchsensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact) determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined thresholds values without changing thetrackpad or touch screen display hardware. Additionally, in someimplementations a user of the device is provided with software settingsfor adjusting one or more of the set of intensity thresholds (e.g., byadjusting individual intensity thresholds and/or by adjusting aplurality of intensity thresholds at once with a system-level click“intensity” parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns and intensities. Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (lift off) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (lift off) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast or other visual property) of graphicsthat are displayed. As used herein, the term “graphics” includes anyobject that can be displayed to a user, including without limitationtext, web pages, icons (such as user-interface objects including softkeys), digital images, videos, animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which is, optionally, made up        of a video player module and a music player module;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, contactsmodule 137 are, optionally, used to manage an address book or contactlist (e.g., stored in application internal state 192 of contacts module137 in memory 102 or memory 370), including: adding name(s) to theaddress book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 138, videoconference 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact module130, graphics module 132, and text input module 134, telephone module138 are, optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in address book 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact module 130, graphics module132, text input module 134, contact list 137, and telephone module 138,videoconferencing module 139 includes executable instructions toinitiate, conduct, and terminate a video conference between a user andone or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, e-mail client module 140 includes executable instructions tocreate, send, receive, and manage e-mail in response to userinstructions. In conjunction with image management module 144, e-mailclient module 140 makes it very easy to create and send e-mails withstill or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in a MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, map module 154, and music player module 146,workout support module 142 includes executable instructions to createworkouts (e.g., with time, distance, and/or calorie burning goals);communicate with workout sensors (sports devices); receive workoutsensor data; calibrate sensors used to monitor a workout; select andplay music for a workout; and display, store and transmit workout data.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, text input module 134, and cameramodule 143, image management module 144 includes executable instructionsto arrange, modify (e.g., edit), or otherwise manipulate, label, delete,present (e.g., in a digital slide show or album), and store still and/orvideo images.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, e-mail client module 140, and browser module 147, calendarmodule 148 includes executable instructions to create, display, modify,and store calendars and data associated with calendars (e.g., calendarentries, to do lists, etc.) in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, the widget creator module 150 are,optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, and text input module 134,search module 151 includes executable instructions to search for text,music, sound, image, video, and/or other files in memory 102 that matchone or more search criteria (e.g., one or more user-specified searchterms) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, and browser module 147, video and music playermodule 152 includes executable instructions that allow the user todownload and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present or otherwise play back videos (e.g., ontouch screen 112 or on an external, connected display via external port124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, notes module153 includes executable instructions to create and manage notes, to dolists, and the like in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, and browser module 147, map module 154 are,optionally, used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions; data on stores and otherpoints of interest at or near a particular location; and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, text input module 134, e-mail client module 140,and browser module 147, online video module 155 includes instructionsthat allow the user to access, browse, receive (e.g., by streamingand/or download), play back (e.g., on the touch screen or on anexternal, connected display via external port 124), send an e-mail witha link to a particular online video, and otherwise manage online videosin one or more file formats, such as H.264. In some embodiments, instantmessaging module 141, rather than e-mail client module 140, is used tosend a link to a particular online video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177 or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event 187 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first lift-off (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second lift-off (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and lift-off of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event 187 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward)and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also includes one or more physical buttons, suchas “home” or menu button 204. As described previously, menu button 204is, optionally, used to navigate to any application 136 in a set ofapplications that are, optionally executed on device 100. Alternatively,in some embodiments, the menu button is implemented as a soft key in aGUI displayed on touch screen 112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above identified elements in FIG. 3 are, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove identified modules corresponds to a set of instructions forperforming a function described above. The above identified modules orprograms (i.e., sets of instructions) need not be implemented asseparate software programs, procedures or modules, and thus varioussubsets of these modules are, optionally, combined or otherwisere-arranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces (“UI”)that is, optionally, implemented on portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Text;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online Video”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Map;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, which            provides access to settings for device 100 and its various            applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 are labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments the touch sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector,” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch-screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch-screen display, a detected contact on the touch-screen actsas a “focus selector,” so that when an input (e.g., a press input by thecontact) is detected on the touch-screen display at a location of aparticular user interface element (e.g., a button, window, slider orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementationsfocus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch-screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch-screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

The user interface figures described below include various intensitydiagrams that show the current intensity of the contact on thetouch-sensitive surface relative to one or more intensity thresholds(e.g., a contact detection intensity threshold IT₀, a light pressintensity threshold IT_(L), a deep press intensity threshold IT_(D),and/or one or more other intensity thresholds). This intensity diagramis typically not part of the displayed user interface, but is providedto aid in the interpretation of the figures. In some embodiments, thelight press intensity threshold corresponds to an intensity at which thedevice will perform operations typically associated with clicking abutton of a physical mouse or a trackpad. In some embodiments, the deeppress intensity threshold corresponds to an intensity at which thedevice will perform operations that are different from operationstypically associated with clicking a button of a physical mouse or atrackpad. In some embodiments, when a contact is detected with anintensity below the light press intensity threshold (e.g., and above anominal contact-detection intensity threshold IT₀ below which thecontact is no longer detected), the device will move a focus selector inaccordance with movement of the contact on the touch-sensitive surfacewithout performing an operation associated with the light pressintensity threshold or the deep press intensity threshold. Generally,unless otherwise stated, these intensity thresholds are consistentbetween different sets of user interface figures.

An increase of intensity of the contact from an intensity below thelight press intensity threshold IT_(L) to an intensity between the lightpress intensity threshold IT_(L) and the deep press intensity thresholdIT_(D) is sometimes referred to as a “light press” input. An increase ofintensity of the contact from an intensity below the deep pressintensity threshold IT_(D) to an intensity above the deep pressintensity threshold IT_(D) is sometimes referred to as a “deep press”input. An increase of intensity of the contact from an intensity belowthe contact-detection intensity threshold IT₀ to an intensity betweenthe contact-detection intensity threshold IT₀ and the light pressintensity threshold IT_(L) is sometimes referred to as detecting thecontact on the touch-surface. A decrease of intensity of the contactfrom an intensity above the contact-detection intensity threshold IT₀ toan intensity below the contact intensity threshold IT₀ is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments IT₀ is zero. In some embodiments IT₀ is greater thanzero. In some illustrations a shaded circle or oval is used to representintensity of a contact on the touch-sensitive surface. In someillustrations a circle or oval without shading is used represent arespective contact on the touch-sensitive surface without specifying theintensity of the respective contact.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90% or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the description of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

User Interfaces and Associated Processes Performing User InterfaceOperations

Many electronic devices have user interfaces for performing operations,such as viewing user interface objects (photos, email message, etc.) anddeleting user interface objects. Some user interface operations, such asdeleting a user interface object from a device or a separate server, aredestructive, meaning that the operation is difficult or impossible toreverse. For example, a user who has unwittingly deleted an emailmessage will, in some cases, have a limited amount of time to recoverthe email message from a trash folder before it is permanently deleted.To prevent such unwitting operations from occurring, some existingmethods cause the electronic device to request confirmation from a userwho has entered an input (e.g., into the electronic device) requestingsuch a destructive operation. One shortcoming of these existing methodsis that they are time consuming and require the user to enter additionalinputs to confirm that the operation should be performed.

In the embodiments described below, an improved method for performinguser interface operations is provided. A gesture is detected that isassociated with a respective operation by a user on a touch-sensitivesurface (e.g., swipe over an email message to delete the email message).In response to detecting the gesture, the device performs the operationwithout requesting confirmation from the user if the gesture had amaximum intensity on the touch-sensitive surface above a first intensitythreshold (e.g., a deep press swipe is interpreted by the device as anindication that the request to perform an operation is trulyintentional). On the other hand, if the maximum intensity of the gestureis below the first intensity threshold, the device requests confirmationthat the user wants to perform the operation, and thus still protectsagainst performance of unwitting destructive operations. Someoperations, such as scrolling, are performed without requestingconfirmation from the user regardless of the intensity of a gestureassociated with the request to perform the operation.

FIGS. 5A-5I illustrate exemplary user interfaces for performing userinterface operations in accordance with some embodiments. The userinterfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIGS. 6A-6B. Whereapplicable, FIGS. 5A-5I include intensity diagrams that show the currentintensity of the contact on the touch-sensitive surface relative to aplurality of intensity thresholds including a first intensity threshold(e.g., “IT_(D)”). In some embodiments, operations similar to thosedescribed below with reference to “IT_(D)” are performed with referenceto a different intensity threshold (e.g., “IT_(L)”).

In some embodiments, the device is an electronic device with a separatedisplay (e.g., display 450) and a separate touch-sensitive surface(e.g., touch-sensitive surface 451). In some embodiments, the device isportable multifunction device 100, the display is touch-sensitivedisplay system 112, and the touch-sensitive surface includes tactileoutput generators 167 on the display (FIG. 1A). For convenience ofexplanation, the embodiments described with reference to FIGS. 5A-5I and6A-6B will be discussed with reference to a touch screen 112, howeveranalogous operations are, optionally, performed on a device with adisplay 450 and a separate touch-sensitive surface 451 in response todetecting the contacts described in FIGS. 5A-5I on the touch-sensitivesurface 451 while displaying the user interfaces shown in FIGS. 5A-5I onthe display 450; in such embodiments, the focus selector is, optionallya cursor or pointer that is displayed at a location corresponding to(e.g., at or near) the location of the contacts (e.g., 1806, 1808 and1810) shown in FIGS. 5A-5I.

FIG. 5A illustrates an exemplary user interface for performing userinterface operations on an electronic device 300 with a touch screendisplay 112. In some embodiments, the device displays one or more userinterface objects (e.g., user interface objects 1804-1 through 1804-4corresponding, respectively, to email conversations 1-4). In particular,FIGS. 5A-5I illustrate examples of deleting an email message from a listof email messages, and also illustrate examples of other user interfaceoperations, such as scrolling through the list of emails, in accordancewith some embodiments.

FIG. 5B illustrates detection of a contact 1806. In some embodiments,particular gestures are associated with a particular respectiveoperation. For example, contact 1806 is included in a swipe gesture overuser interface object 1804-1. FIG. 5B illustrates an example ofembodiments in which a swipe gesture over an e-mail message (userinterface item 1804-1) is interpreted as a request to delete or archivethe message. In some embodiments, the swipe gesture is considered overthe email message if the gesture begins in a predefined boundary of theemail message. In some embodiments, the swipe gesture is considered overthe email message if a substantial portion of the gesture occurs withinthe predefined boundary (or within a predefined area in which arepresentation of the email message is displayed).

In the example shown in FIG. 5B, contact 1806 has an intensity below arespective intensity threshold (e.g., IT_(D)). In this example, thedevice detects the gesture and, based on predefined criteria, eitherrequests confirmation that the user wants to delete email message (e.g.,if the criteria are not met) or deletes the email message withoutrequesting confirmation from the user (e.g., if the criteria are met).In some embodiments, the predefined criteria include that a respectiveintensity (e.g., the maximum intensity) of the gesture is above apredefined threshold (e.g., IT_(D)). It is envisioned that the intensityof contact 1806 while gesture is detected over the e-mail message couldbe defined and measured in any number of ways. For example, in someembodiments, the intensity is measured at the beginning of the gesture.In some embodiments, the average intensity of the gesture is used. Othermetrics for measuring and defining the intensity of the gesture will beapparent to those with skill in the art.

FIG. 5C illustrates the continuation of contact 1806 to form a swipegesture across user interface object 1804-1. Contact 1806 in both FIGS.5B and 5C has an intensity below the deep press intensity threshold. Asa result, the device requests confirmation (e.g., displays an affordancewith the word “Delete?”) that the user wants to delete the emailmessage. Requesting confirmation to perform an operation such as adestructive operation (such as deleting a user interface object) for lowintensity gestures enables the device to protect against unintendedoperations that are difficult or impossible to reverse. In someembodiments, the user optionally selects the affordance (either with aseparate contact or a continuation of the same gesture) to inform thedevice to proceed with the operation. In some embodiments, a separategesture, distinct from selection of the affordance, cancels theoperation. For example, in some embodiments, a second swipe over theemail cancels the request to delete the email. In some embodiments, anyof a plurality of gestures other than a gesture that includes selectionof the affordance cancels the delete operation. In this example, contact1806 is also below the light press intensity threshold. In this example,no additional functionality is associated with the light press intensitythreshold. However, in some other embodiments, additional functionalityis associated with the light press input (e.g., the light pressintensity threshold is an intensity threshold used to identify lightpress inputs for activating affordances such as the delete affordance inFIG. 5B, the edit affordance in FIG. 5B and/or opening one of theconversations in response to detecting a light press input on one ofuser interface objects 1804 that includes an increase of a contact froman intensity below IT_(L) to an intensity above IT_(L)).

FIG. 5D is analogous to FIG. 5B with the difference that contact 1808shown in FIG. 5D has an intensity above the deep press intensitythreshold IT_(D) (e.g., contact 1806 in FIG. 5B with an intensity belowIT_(D)). FIG. 5E shows a continuation of the gesture that includescontact 1808. FIG. 5E is analogous to FIG. 5C with the difference thatcontact 1808 shown in FIG. 5E has an intensity above the deep pressintensity threshold (e.g., contact 1806 in FIG. 5C). For brevity,additional details already described with reference to FIGS. 5B and 5Care not repeated here with reference to FIGS. 5D and 5E, respectively.In some embodiments, because contact 1808 has a maximum intensity aboveIT_(D) while over the email message, the email message is deletedwithout requesting confirmation from the user. In this example, thedevice determines on the basis of a high intensity of the contact thatthe gesture is not accidental, and therefore proceeds with the operation(e.g., deletion) without requiring the user to enter more user inputs(e.g., a confirmation input), thus saving the user time and promotingefficiency. In some embodiments, contact 1808 has an intensity aboveIT_(D) throughout the gesture shown in FIGS. 5D-5E. In some embodiments,contact 1808 has an intensity above IT_(D) at the beginning of thegesture shown in FIGS. 5D-5E and an intensity below IT_(D) at the end ofthe gesture shown in FIGS. 5D-5E. In some embodiments, contact 1808 hasan intensity below IT_(D) at the beginning of the gesture shown in FIGS.5D-5E and an intensity above IT_(D) at the end of the gesture shown inFIGS. 5D-5E.

In some embodiments, it is helpful to display a dramatic animation(e.g., an animation of glass shattering or a representation of the emailmessage being “crumpled up”) that catches the user's attention to informthe user that the destructive operation has been performed. In someembodiments, after displaying the animation that corresponds to thedestructive operation, the user is provided with an option to undo thedestructive operation (e.g., display an “undo” affordance orinstructions to shake to undo). FIG. 5F shows a still-frame illustrationof such an animation. In this case, the animation displays the words“DELETING” in dramatic fashion.

FIG. 5G illustrates that, after the animation described with referenceto FIG. 5F, the email message is removed from the list. In someembodiments, one or more additional email messages that were previouslynot visible (e.g., a user would have to scroll through the list of emailmessages in order to view them) are now visible due to the removal ofuser interface object 1804-1. For example, user interface object 1804-5is now visible to the user without scrolling.

In some embodiments, certain inputs associated with certain operationscan be performed without requesting confirmation from the userregardless of the intensity of contacts corresponding to the inputs. Forexample, FIG. 5H illustrates a vertical swipe input including upwardmovement of contact 1810. In this example, vertical swipe inputperformed with contact 1810 is interpreted by the device as a request toscroll through the list of email messages. FIG. 5I shows the resultingchange in the displayed email messages (the list has been scrolled suchthat user interface objects 1804-5 through 1804-7 are now displayed).The maximum intensity of vertical swipe gesture performed with contact1810 is below the deep press intensity threshold (and the light pressintensity threshold, for that matter). However, because the operation ofscrolling, in this example, does not require user confirmation, the listis scrolled without requesting user confirmation. In some embodiments,operations associated with light press gestures are categorized asrequiring user confirmation or not requiring user confirmation based onthe ease with which they can be reversed (e.g., whether they aredestructive operations or non-destructive operations).

FIGS. 6A-6B are flow diagrams illustrating a method 1900 of performinguser interface operations in accordance with some embodiments. Themethod 1900 is performed at an electronic device (e.g., device 300, FIG.3, or portable multifunction device 100, FIG. 1A) with a display and atouch-sensitive surface. In some embodiments, the display is a touchscreen display and the touch-sensitive surface is on the display. Insome embodiments, the display is separate from the touch-sensitivesurface. Some operations in method 1900 are, optionally, combined and/orthe order of some operations are, optionally, changed.

As described below, the method 1900 provides an intuitive way to performuser interface operations. The method reduces the cognitive burden on auser when performing user interface operations, thereby creating a moreefficient human-machine interface. For battery-operated electronicdevices, enabling a user to perform user interface operations faster andmore efficiently conserves power and increases the time between batterycharges.

The device displays (1902) a user interface on a display of a device(e.g., the user interface displayed on touch screen 112 of device 300,FIG. 5A). The device detects (1904) a gesture by a user on atouch-sensitive surface that includes a contact (e.g., contact 1806,FIG. 5B) that corresponds to a focus selector at a respective locationin a user interface. The gesture is associated with a respectiveoperation.

In some embodiments, the gesture is (1906) a swipe gesture of a contactthat corresponds to movement of the focus selector across arepresentation of an item in a list of items (e.g., a message orconversation in an email inbox). In some embodiments, the user interfaceincludes (1908) a plurality of user interface objects, and therespective location corresponds to a respective object in the pluralityof user interface objects. In some embodiments, the respective operationis (1910) a destructive operation (e.g., a delete operation).

In response to detecting the gesture, in accordance with a determinationthat the contact has a maximum intensity below a first intensitythreshold, the device requests (1912) confirmation that the user wantsthe device to perform the respective operation (e.g., to confirm thatthe user did not accidentally perform the gesture). For example, FIGS.5C-5D illustrate examples of a gesture with a maximum intensity belowIT_(D) and subsequent request for confirmation to delete an emailmessage. In response to the gesture, in accordance with a determinationthat maximum intensity of the contact is above the first intensitythreshold, the device performs the respective operation withoutrequesting confirmation that the user wants the device to perform therespective operation. For example, FIGS. 5D-5E illustrate an example ofa gesture with a maximum intensity above IT_(D) and subsequent deletionof an email message without requesting confirmation. In someembodiments, the first intensity threshold is an intensity thresholdthat is higher than an input-detection intensity threshold at which thecontact is initially detected. In some embodiments, the devicedetermines whether to request confirmation or to perform the operationwithout requesting confirmation based on whether the gesture met theconfirmation criteria. In some embodiments, the confirmation criteriaare met when contact (e.g., contact 1808 in FIGS. 5D-5E) has anintensity that is maintained (e.g., continuously maintained) aboveIT_(D) throughout the gesture. In some embodiments, the confirmationcriteria are met when the contact (e.g., contact 1808 in FIGS. 5D-5E)has an intensity above IT_(D) at the beginning of the gesture (or priorto detecting movement of the contact) without regard to whether or notthe contact has an intensity above IT_(D) at the end of the gesture. Insome embodiments, the confirmation criteria are met when the contact(e.g., contact 1808 in FIGS. 5D-5E) has an intensity above IT_(D) at theend of the gesture (or after ceasing to detect movement of the contact)without regard to whether or not the contact has an intensity aboveIT_(D) at the beginning of the gesture.

In some embodiments, requesting confirmation that the user wants thedevice to perform the respective operation includes (1914) displaying aconfirmation message that includes an option to proceed with performingthe respective operation. In some embodiments, the confirmation messageincludes an explicit option to cancel performance of the respectiveoperation. In some embodiments, the confirmation message does notinclude an explicit option to cancel performance of the respectiveoperation, but tapping/pressing while a focus selector is outside of theconfirmation message cancels performance of the respective operation. Insome embodiments, the confirmation identifies (1916) the respectiveoperation that is to be performed (e.g., a dialogue box that says “doyou want to delete this message? Yes/No” or an affordance that simplysays “Delete?” as in FIG. 5C).

In some embodiments, it is helpful to display a dramatic animation thatcatches the user's attention to inform the user that the destructiveoperation has been performed. In some embodiments, the respectiveoperation is (1918) a delete operation, and performing the operationincludes displaying an animation that crumples the respective userinterface object (e.g., crumpling the object like a piece of paper). Insome embodiments, the operation is (1920) a delete operation, andperforming the operation includes displaying an animation that shattersthe respective user interface object (e.g., shattering the object like apiece of glass). For example, FIG. 5F shows a still-frame of ananimation of the word “DELETING” shattering like glass. In someembodiments, after displaying the animation that corresponds to thedestructive operation, the user is provided with an option to undo thedestructive operation (e.g., display an “undo” affordance orinstructions to shake to undo). In some embodiments, the operation is adelete operation, and performing the operation includes displaying ananimation that folds the respective user interface object up (e.g.,folding the respective user interface object with itself and/or foldinga plurality of user interface objects including the respective userinterface object). In some embodiments, the operation is a deleteoperation, and performing the operation includes displaying an animationof the respective user interface object moving backwards into thedisplay (e.g., the respective user interface object moves backwards andfades out).

In some embodiments, the device detects (1922) one or more inputs thatinclude contacts with maximum intensity below the first intensitythreshold. In response to detecting the one or more inputs, the deviceperforms (1924) one or more corresponding operations (e.g.,non-destructive operations such as scrolling operations or email viewingoperations) without requesting confirmation from the user. For example,a user can view or scroll a list of email messages using one or morecontacts with intensities below the first intensity threshold, as shownin FIGS. 5H-5I.

It should be understood that the particular order in which theoperations in FIGS. 6A-6B have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,those listed in the fifth paragraph of the Description of Embodiments)are also applicable in an analogous manner to method 1900 describedabove with respect to FIGS. 6A-6B. For example, the contacts, gestures,user interface objects, intensity thresholds, focus selectors,animations described above with reference to method 1900 optionally haveone or more of the characteristics of the contacts, gestures, userinterface objects, intensity thresholds, focus selectors, animationsdescribed herein with reference to other methods described herein (e.g.,those listed in the fifth paragraph of the Description of Embodiments).For brevity, these details are not repeated here.

In accordance with some embodiments, FIG. 7 shows a functional blockdiagram of an electronic device 2000 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 7 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein. As shown in FIG.7, an electronic device 2000 includes a display unit 2002 configured todisplay a user interface, a touch-sensitive surface unit 2004 configuredto detect a gesture by a user on the touch-sensitive surface unit thatincludes a contact that corresponds to a focus selector at a respectivelocation in the user interface, wherein the gesture is associated with arespective operation, one or more sensor units 2006 configured to detectintensity of contacts with the touch-sensitive surface unit 2004; and aprocessing unit 2008 coupled to the display unit 2002, thetouch-sensitive surface unit 2004 and the one or more sensor units 2006.In some embodiments, the processing unit 2008 includes a confirmationrequesting unit 2010, an operation performing unit 2012, and ananimating unit 2014.

In some embodiments, the user interface includes a plurality of userinterface objects; and the respective location corresponds to arespective object in the plurality of user interface objects.

The processing unit 2008 is configured to: in response to detecting thegesture: in accordance with a determination that the contact has amaximum intensity below a first intensity threshold, requestconfirmation (e.g., with confirmation requesting unit 2010) that theuser wants the device to perform the respective operation; and inaccordance with a determination that the maximum intensity of thecontact is above the first intensity threshold, perform the respectiveoperation (e.g., with operation performing unit 2012) without requestingconfirmation that the user wants the device to perform the respectiveoperation.

In some embodiments, the gesture is a swipe gesture of a contact thatcorresponds to movement of the focus selector across a representation ofan item in a list of items.

In some embodiments, requesting confirmation (e.g., with confirmationrequesting unit 2010) that the user wants to perform the respectiveoperation includes displaying a confirmation message that includes anoption to proceed with performing the respective operation.

In some embodiments, the confirmation identifies the respectiveoperation that is to be performed.

In some embodiments, the respective operation is a destructiveoperation.

In some embodiments, the processing unit 2008 is further configured to:detect one or more inputs that include contacts with maximum intensitybelow the first intensity threshold; and in response to detecting theone or more inputs, perform one or more corresponding operations withoutrequesting confirmation from the user.

In some embodiments, the respective operation is a delete operation; andperforming the operation includes displaying an animation (e.g., withanimating unit 2014) that crumples the respective user interface object.

In some embodiments, the operation is a delete operation; and performingthe operation includes displaying an animation (e.g., with animatingunit 2014) that shatters the respective user interface object.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 6A-6B are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 7.For example, displaying operation 1902, detecting operation 1904, andcrumple animating operation 1918 are, optionally, implemented by eventsorter 170, event recognizer 180, and event handler 190. Event monitor171 in event sorter 170 detects a contact on touch-sensitive display112, and event dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub-event,such as selection of an object on a user interface. When a respectivepredefined event or sub-event is detected, event recognizer 180activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 optionally utilizes or calls dataupdater 176 or object updater 177 to update the application internalstate 192. In some embodiments, event handler 190 accesses a respectiveGUI updater 178 to update what is displayed by the application.Similarly, it would be clear to a person having ordinary skill in theart how other processes can be implemented based on the componentsdepicted in FIGS. 1A-1B.

Displaying Additional Information in Response to a User Contact

Many electronic devices have graphical user interfaces that include userinterface objects displayed at specific locations on the display. Insome instances, one or more user interface objects are associated withhidden information that is revealed when a user places a cursor orcontact over the user interface object for a predefined period of time(e.g., tooltips) or clicks and holds on a user interface object for apredefined period of time (e.g., a back button on a browser). Theseinstances require the user to wait for the predefined period of time toelapse to see the initially hidden information. It would be advantageousto provide the user with the option to avoid waiting and get immediatedisplay of the additional information. In some instances, a singleactivation region or user interface object is associated with aplurality of operations of the device (e.g., a back button on a browseris associated with both navigating to a previous webpage and displayinga pop-up list of previously visited webpages). In these instances, atime delay is sometimes introduced as a way to determine which operationof the plurality of operations to perform in response to a user inputassociated with the activation region or user interface object. But suchdelays interrupt a user's workflow. Providing an intuitive way toimmediately perform a particular operation can make a user's interactionwith the device much more efficient.

The embodiments described below provide new, improved methods ofdisplaying additional information (or activating user interface objects)using a touch-sensitive surface and sensors that detect the intensity(e.g., pressure) of a contact on the touch-sensitive surface. To avoidwaiting a predefined delay time in order to view additional informationassociated with a user interface object or a region of a user interface,the user has the option to apply an intensity (e.g., pressure) ofcontact greater that a predefined intensity threshold to immediately seethe additional information. For example, the user can immediatelydisplay a tool tip or pop-up menu by pressing on the touch-sensitivesurface with an intensity above the intensity threshold, without havingto wait for a delay time. Similarly, for a back button on a browser, theuser can immediately display a list of previously accessed webpages bypressing on the touch-sensitive surface with an intensity above theintensity threshold. On the other hand, if the user does not press withsufficiently intensity, the additional information is not displayeduntil the delay time has elapsed. Accordingly, the described embodimentsprovide the user with a more efficient way to interact with userinterface objects.

FIGS. 8A-8N illustrate exemplary user interfaces for displayingadditional information associated with a location on a display based oncontact intensity (e.g., pressure) and contact timing (e.g., duration)in accordance with some embodiments. The user interfaces in thesefigures are used to illustrate the processes described below, includingthe processes in FIGS. 9A-9B. FIGS. 8A-8N include intensity diagramsthat show the current intensity of the contact on the touch-sensitivesurface relative to a plurality of intensity thresholds including arespective threshold (e.g., “IT_(D)”). In some embodiments, operationssimilar to those described below with reference to IT_(D) are performedwith reference to a different intensity threshold (e.g., “IT_(L)”).

FIG. 8A illustrates a user interface (e.g., a webpage), with a pluralityof selectable objects (e.g., 3606-1 and 3606-2), that is displayed on adisplay 450. FIGS. 8A-8C illustrate displaying additional information(e.g., by scrolling the webpage) in response to detecting a contactwithout waiting for a predefined delay time from the time of detectingthe contact, when the contact has an intensity that is above (e.g.,greater than) an intensity threshold.

In FIG. 8A, at a time prior to T0, no contact is present or detected ontouch-sensitive surface 451 and focus selector 3607-a is remote fromscroll arrow 3606-4 in scroll bar 3606-3. In FIG. 8B, at time T0, acontact (e.g., contact 3605 in FIG. 8B) is detected on thetouch-sensitive surface 451. In response to detecting the contact on thetouch-sensitive surface 451, the device instructs display 450 toposition a focus selector (e.g., focus selector 3607-a in FIG. 8B) at alocation on display 450 (e.g., over scroll arrow 3606-4 in scroll bar3606-3 in FIG. 8B). In FIG. 8C, after time T1 and prior to time T2,while focus selector 3607-a is still positioned at the location on thedisplay 450 (e.g., over scroll arrow 3606-4 in scroll bar 366-3 in FIG.8C), the intensity of the contact (e.g., contact 3605 in FIG. 8C) on thetouch-sensitive surface 451 exceeds the intensity threshold IT_(D). Whenthe contact has an intensity that is above a predefined intensitythreshold, additional information (e.g., additional selectable objects3606-6 and 3606-7) is displayed on the display 450 (e.g., by scrollingthe webpage) without waiting for a predefined delay time to elapse(e.g., without waiting until time T2 or without waiting until apredefined delay time, T_(delay)=T2−T0, has elapsed). In other words, ifthe user places a contact with an intensity above the intensitythreshold when the focus selector 3607-a is over scroll arrow 3606-4,the user interface is scrolled, even if the delay time has not yetelapsed. In some embodiments, the portion of the user interface thatcontrols scrolling of the user interface includes a displayed scrolluser interface (e.g., as illustrated in FIG. 8A). In some embodiments,the portion of the user interface that controls scrolling of the userinterface is a hidden hit region that is not displayed, but is presentat the edges of a scrollable window of an application. For example, ifuser moves cursor 3607 to a bottom edge of the display while moving arespective icon or other user interface object or while selecting text,the device scrolls the user interface either in response to detectingthe cursor in the hidden hit region for longer than the delay time or inresponse to detecting an increase in the intensity of the contact abovethe predefined intensity threshold.

FIGS. 8D-8G illustrate waiting until a predefined delay time has elapsedfrom the time of detecting a contact on the touch-sensitive surface 451(or from a time that the contact reached a lower intensity threshold,such as IT_(L)) to display additional information (e.g., by scrollingthe webpage) in response to the detected contact, when the contact hasan intensity that is below (e.g., lower than) an intensity threshold(e.g., “IT_(D)”).

In FIG. 8D, at a time prior to T0, no contact is present or detected ona touch-sensitive surface 451 and focus selector 3607-a is remote fromscroll arrow 3606-4 in scroll bar 3606-3. In FIG. 8E, at time T0, acontact (e.g., contact 3608 in FIG. 8E) is detected on thetouch-sensitive surface 451. In response to detecting the contact on thetouch-sensitive surface 451, the device instructs the display 450 toposition a focus selector (e.g., focus selector 3607-b in FIG. 8E) at arespective location on the display 450 (e.g., at edge 3606-4 of scrollbar 3606-3 in FIG. 8E). In FIG. 8F, at a time prior to time T2, whilefocus selector 3607-b is still positioned at the respective location onthe display 450 (e.g., over scroll arrow 3606-4 in scroll bar 3606-3 inFIG. 8F), the intensity of the contact (e.g., contact 3608 in FIG. 8F)on the touch-sensitive surface 451 is below the intensity thresholdIT_(D). While contact 3608 has an intensity that is below the intensitythreshold and while focus selector 3607-b is still positioned at therespective location on the display 450, the device does not displayadditional information associated with the respective location of focusselector 3607-b until a predefined delay time (e.g., predefined delaytime, T_(delay)=T2−T0) has elapsed or until time T2. In FIG. 8G, whilethe intensity of the contact (e.g., contact 3608 in FIG. 8G) on thetouch-sensitive surface 451 is still below the intensity thresholdIT_(D), after a predefined delay time (T_(delay)=T2−T0) has elapsed orafter time T2, and while the focus selector 3607-b is still positionedat the location on the display 450 (e.g., over scroll arrow 3606-4 inscroll bar 3606-3 in FIG. 8G), additional information (e.g., additionalselectable objects 3606-6 and 3606-7) is displayed on the display 450(e.g., by scrolling the webpage). For example, if the user places acontact with an intensity below the intensity threshold over a scrollarrow in a scroll region and waits longer than the delay time, the userinterface is scrolled accordingly. In some embodiments, the delay timeT_(delay)=T2−T1, and the contact reaches a lower intensity threshold(e.g., “IT_(L)”) at time T1 and the additional information is displayedon the display after waiting until the intensity of the contact has beenmaintained above intensity threshold IT_(L) from time T1 until time T2.

In other words, in some embodiments, the device determines if theintensity of the contact is above an intensity threshold while the focusselector is at a respective location on the display. If the intensity ofthe contact is above the intensity threshold, the device does not waitfor the predefined delay time to display the additional information onthe display, but rather displays the additional information immediately.On the other hand, if the intensity of the contact is below theintensity threshold, the device waits until the predefined delay time todisplay the additional information on the display, and thereforedisplays the additional information at a later time (e.g., as determinedfrom the predefined delay time). As a result, the user can display theadditional (e.g., initially undisplayed) information associated with alocation on the display corresponding to a contact, sooner—withouthaving to wait for a predefined delay time—if the user increases theintensity of the contact above the intensity threshold.

In some embodiments, while the focus selector is displayed at arespective location, the device determines if a predefined delay timehas elapsed from the time the contact was detected. If the predefineddelay time has elapsed since the detection of the contact, the devicedisplays additional information on the display 450. On the other hand,if the predefined delay time has not elapsed, the device determines(e.g., checks repeatedly, iteratively, or a plurality of times) if theintensity of the contact is above the predefined threshold. If thedevice determines the intensity of the contact to be above thepredefined threshold, the device displays the additional informationwithout waiting until the predefined delay time has elapsed.

FIG. 8H illustrates a user-interface (e.g., a webpage) that is displayedon a touch-screen 112. FIGS. 8H-8J further illustrate displayingadditional information (e.g., a browsing history, including a list ofpreviously accessed webpages) in response to a contact detected directlyon touch-screen 112 without waiting for a predefined delay time from thetime of detecting the contact, when the contact has an intensity (e.g.,pressure) that is above (e.g., greater than) an intensity threshold(e.g., IT_(D)).

In FIG. 8H, at a time prior to T0, no contact is present or detected ontouch-screen 112 at a location corresponding to browser back button 3610(however, a contact is, optionally, present at another location ontouch-screen 112). In FIG. 8I, at time T0, a contact (e.g., contact 3609in FIG. 8I) is detected on the touch-screen 112 at a respective location(e.g., at the location of a back button 3610 in FIG. 8I). In someembodiments, when the device has a touch-screen display and the contactis detected on the touch-screen, the position of a focus selectorcoincides with the position of the contact on the touch-screen. In FIG.8J, after time T1 and prior to time T2, while the contact 3609 is stillpositioned at the respective location on the touch-screen 112 (e.g., atthe location of a back button 3610 in FIG. 8J), the intensity of thecontact (e.g., contact 3609 in FIG. 8J) on touch-screen 112 exceeds theintensity threshold IT_(D). When the contact has an intensity that isabove a predefined intensity threshold, additional information (e.g., abrowsing history, including a list 3611 of previously accessed webpages)is displayed on the touch-screen 112 without waiting for a predefineddelay time to elapse (e.g., without waiting until time T2 or withoutwaiting until a predefined delay time, T_(delay)=T2−T0, has elapsed). Inother words if the user places a contact with an intensity above theintensity threshold IT_(D) on the browser back button, the browserhistory is displayed even if the delay time has not yet elapsed.

FIGS. 8K-8N illustrate waiting until a predefined delay time has elapsedfrom the time of detecting a contact at a respective location ontouch-screen 112 to display additional information (e.g., a browsinghistory, including a list 3611 of previously accessed webpages,sometimes called a browser history) corresponding to the detectedcontact, when the contact has an intensity that is below (e.g., lowerthan) an intensity threshold IT_(D).

In FIG. 8K, at a time prior to T0, no contact is present or detected onthe touch-screen 112 at a location corresponding to browser back button3610 (however, a contact is, optionally, present at another location ontouch-screen 112). In FIG. 8L, at time T0, a contact (e.g., contact 3613in FIG. 8L) is detected on the touch-screen 112 at a locationcorresponding to browser back button 3610. In some embodiments, thelocation of the contact on the touch-screen 112 coincides with thelocation of a focus selector on the touch-screen 112 (e.g., at thelocation of a back button 3610 in FIG. 8L). In FIG. 8M, at a time priorto time T2, while the contact (or the focus selector) is stillpositioned at the respective location on the touch-screen 112 (e.g., atthe location of a back button 3610 in FIG. 8M), the intensity of thecontact (e.g., contact 3613 in FIG. 8L) on the touch-screen 112 is belowthe intensity threshold IT_(D). When the contact has an intensity thatis below the intensity threshold and the contact (or the focus selector)is still positioned at the respective location on the touch-screen 112,the device does not display additional information until a predefineddelay time (e.g., predefined delay time, T_(delay)=T2−T0) has elapsed oruntil time T2. In FIG. 8N, after a predefined delay time(T_(delay)=T2−T0) has elapsed or after time T2 while the contact (or afocus selector corresponding to the contact) is still positioned at therespective location on the touch-screen 112 (e.g., at the location of aback button 3610 in FIG. 8N), additional information (e.g., a browsinghistory, including a list 3611 of previously accessed webpages) isdisplayed on the touch-screen 112. In other words if the user places acontact with an intensity below the intensity threshold IT_(D) on thebrowser back button and waits longer than the delay time, the browserhistory is displayed.

FIGS. 9A-9B are flow diagrams illustrating a method 3700 of displayingadditional information associated with a location on a display based oncontact intensity (e.g., pressure) and contact timing (e.g., duration)in accordance with some embodiments. The method 3700 is performed at anelectronic device (e.g., device 300, FIG. 3, or portable multifunctiondevice 100, FIG. 1A) with a display and a touch-sensitive surface. Insome embodiments, the display is a touch screen display and thetouch-sensitive surface is on the display. In some embodiments, thedisplay is separate from the touch-sensitive surface. The deviceincludes one or more sensors to detect intensity of contacts with thetouch-sensitive surface. Some operations in method 3700 are, optionally,combined and/or the order of some operations is, optionally, changed.

As described below, the method 3700 provides an intuitive way to displayadditional (e.g., initially undisplayed) information associated with alocation on a display based on contact intensity (e.g., pressure) andcontact timing (e.g., duration). The method reduces the cognitive burdenon a user when displaying the additional (e.g., initially undisplayed)information, thereby creating a more efficient human-machine interfaceby enabling a user to skip a delay time and immediately access theadditional information. For battery-operated electronic devices,enabling a user to display additional (e.g., initially undisplayed)information faster and more efficiently conserves power and increasesthe time between battery charges.

The device detects (3702) a contact on the touch-sensitive surface whilea focus selector corresponding to the contact is at a respectivelocation on the display that is associated with additional informationthat is not initially displayed on the display (e.g., the additionalinformation is not displayed immediately prior to detecting movement ofthe focus selector across the display to the respective location ordetecting the contact on the touch screen at the respective location).In some embodiments, the additional information is “associated with” therespective location in that, when a predefined gesture (e.g., a fingerpress input) is performed at the respective location, the additionalinformation is displayed on the display.

In some embodiments, the device detects a gesture including movement ofthe contact across the touch-sensitive surface that corresponds tomovement of the focus selector to the respective location on the display(e.g., movement of a cursor across the display in response to movementof a contact on a touchpad). In such embodiments, the additionalinformation is not displayed immediately prior to detecting movement ofthe focus selector across the display to the respective location. Forexample, as explained with reference to FIGS. 8A-8G, the device detectscontact 3605 on the touch-sensitive surface 451 that is separate fromdisplay 450. In this example, a focus selector (e.g., cursor 3607 inFIGS. 8A-8G) corresponding to contact 3608 on touch-sensitive surface451 is positioned at a respective location on display 450 (e.g., overscroll arrow 3606-4 in scroll bar 3606-3 in FIG. 8B) and moves inaccordance with movement of contact 3605. Additional information (e.g.,additional selectable objects 3606-6 and 3606-7 displayed on display450, FIG. 8C) associated with the position of focus selector 3607-a isnot initially displayed on display 450.

In some embodiments, the contact is a finger contact. In someembodiments, the additional information is not displayed immediatelyprior to detecting the contact on the touch screen at the respectivelocation. In some embodiments, the device detects the contact on aportion of the touch-sensitive surface that corresponds to therespective location (e.g., the device detects the contact at a locationof a button associated with additional information on a touch screendisplay). For example, as explained with reference to FIGS. 8I-8N, thedevice detects contact 3609 on the touch-screen 112 at a respectivelocation (e.g., at the location of back button 3610 in FIG. 81). In someembodiments, as shown in FIG. 8I, when the device has a touch-screendisplay (e.g., touch screen 112) and the contact (e.g., contact 3609,FIG. 8I) is detected on the touch-screen, the position of a focusselector coincides with the position of the contact. Additionalinformation (e.g., a browsing history, including a list 3611 ofpreviously accessed webpages, FIG. 8J) associated with the position ofthe focus selector is not initially displayed on touch screen 112.

In some embodiments, the device displays (3704) a user interface objecton the display. In some embodiments, the user interface object isassociated with (3706) the additional information that is not initiallydisplayed on the display; and the respective location corresponds to alocation of the user interface object on the display (e.g., theadditional information is associated with an icon or other displayedelement of the user interface). In some embodiments, the respectivelocation is not associated with a particular user interface object onthe display (e.g., the device detects the contact or cursor in anactivation region or hidden hit region of the touch-sensitive surfaceand/or display that, when activated by waiting for the delay time orincreasing the intensity of the contact above an intensity threshold,triggers display of the additional information).

In some embodiments, the additional information includes (3708) help forthe user interface object (e.g., information describing the userinterface object and one or more options for retrieving further helprelated to the user interface objects, such as a hyperlink or searchbox). In some embodiments, the additional information includes (3710) adescription of one or more functions of the user interface object. Insome embodiments, the additional information includes a briefdescription of the user interface object and/or a description of thefunctionality associated with the user interface object. For example, ifthe user interface object is a ‘create a bookmark’ icon in the browser,the additional information is, optionally: ‘this creates a new bookmark;bookmarks are a way to save your favorite sites.’

In some embodiments, the additional information includes (3712) a menuwith selectable options related to the user interface object. Forexample, if the user interface object is a file icon, the additionalinformation includes a menu with selectable options such as ‘open,’‘edit,’ ‘print,’ ‘copy,’ ‘delete,’ ‘rename’ and the like.

In some embodiments, the user interface object is (3714) a back button.For example, the user interface object is back button of a web browseror a file browser such as back button 3610 shown in FIGS. 8H-8N. In someembodiments (e.g., where the user interface object is a back button),the additional information includes a browsing history that includes alist of representations of previously accessed information. For example,as shown in FIGS. 8J and 8N, the additional information includes abrowsing history, including a list 3611 of previously accessed webpages.In this example, in response to detecting intensity of the contact abovethe respective intensity threshold (e.g., “IT_(D)”) or detecting thecontact for longer than the predefined delay time while the focusselector is over the back button, the device displays a list ofpreviously visited websites or folders. In some embodiments, asdescribed with reference to FIG. 8J, in response to detecting intensityof contact 3609 on touch screen 112 that is above the respectiveintensity threshold, the device displays a list 3611 of previouslyvisited websites or folders on touch screen 112. In some embodiments, asdescribed with reference to FIG. 8N, in response to detecting contact3613 for longer than the predefined delay time (T_(delay)=T2−T0) whilethe focus selector (coinciding with contact 3613 on touch screen 112) isover back button 3610, the device displays list 3611 of previouslyvisited websites or folders.

In some embodiments, the respective location corresponds to (3718) anedge of a user interface for navigating through an electronic document.In some embodiments, the edge of the user interface for navigatingthrough an electronic document is a scroll bar. For example, as shown inFIGS. 8A-8E, the respective location corresponds to a scroll arrow3606-4 in scroll bar 3606-3 for navigating through an electronicdocument, where scroll bar 3606-3 is located at the bottom edge of theuser interface shown on display 450. In some embodiments, the edge ofthe user interface for navigating through the electronic document is aportion of the electronic document that is proximate to an edge of anapplication window displaying the electronic document. For example, insome circumstances a user selecting a portion of an electronic document(e.g., by dragging a cursor or contact over text in a word processingdocument or on a webpage) will reach the edge of the electronic documenton the display. In this example, if the device would otherwise wait fora delay period (e.g., 0.1, 0.2, 0.3, 0.4 or 0.5 seconds) to elapsebefore scrolling the electronic document, the device will,alternatively, begin scrolling the electronic document in response to anincrease in intensity above a respective intensity threshold (e.g.,IT_(D)) before the delay period has elapsed.

In some embodiments (e.g., where the respective location corresponds toa hidden hit region at an edge of a user interface for navigatingthrough an electronic document), the additional information includes aportion of the electronic document that was not displayed immediatelyprior to detecting the contact while the focus selector is at therespective location. For example, when the focus selector is at or nearan edge of an application window while the user is selecting objects(e.g., file icons in a file manager application) or content (e.g., textin a word processing document) in the application window or moving auser interface object (e.g., a file icon in a file manager application)within the application window, the application window is scrolled whenthe focus selector pauses at the edge of the user interface for longerthan the predefined delay time or if a press input above the respectiveintensity threshold is detected while the focus selector is at or nearthe edge of the application window. Scrolling the application window inthis way enables the user to keep moving the user interface object oralternatively enables the user to keep selecting the objects or contentwithout interruption (e.g., without putting a currently selected userinterface object down or without unselecting previously selectedcontent).

For example, in response to detecting intensity of the contact above therespective intensity threshold or detecting the contact for longer thanthe predefined delay time while the focus selector is at an edge of theuser interface for navigating through the electronic document, thedevice scrolls the electronic document. In particular, as explained withreference to FIG. 8C, in response to detecting intensity of contact 3605above the respective intensity threshold IT_(D), while focus selector3607-a is over scroll arrow 3606-4 in scroll bar 3606-3, where scrollbar 3606-3 is located at the bottom edge of the user interface shown ondisplay 450, the device scrolls the electronic document to displayadditional information (e.g., additional selectable objects 3606-6 and3606-7). Similarly, as explained with reference to FIG. 8G, in responseto detecting contact 3608 for longer than the predefined delay time(e.g., longer than predefined delay time T_(delay)=T2−T0) while focusselector 3607-b is over scroll arrow 3606-4 in scroll bar 3606-3, thedevice scrolls the electronic document.

As another example, when the focus selector is proximate to a scroll baror near an edge of an application window in which the electronicdocument is displayed, the device scrolls the document when the focusselector pauses in the location for longer than the predefined delaytime or if a press input above the respective intensity threshold isdetected. In some embodiments, the electronic document is scrolled inaccordance with a determination that a user interface object wascurrently selected and being moved in accordance with movement of thefocus selector when the press input was detected. For example, if theuser is dragging a representation of a file or program (e.g., a file orprogram icon) in a window of a file manager application (e.g., a systemfile manager such as Finder from Apple Inc. of Cupertino, Calif. or amedia manager such as iPhoto from Apple Inc. of Cupertino, Calif. oriTunes from Apple Inc. of Cupertino, Calif.), and the user drags therepresentation of the file or program to an edge of the window of thefile manager application and pauses for longer than the predefined delaytime or increases the intensity of the contact over the respectiveintensity threshold while at the edge of the virtual desktop, the devicewill scroll the window of the file manager program.

In some embodiments, the respective location corresponds to (3720) anedge of the display. For example, the respective location is located onan area or strip within a predefined distance of the edge of the display(e.g., 0.1, 0.5, or 1.0 mm, or 5, 10 or other appropriate number ofpixels). In some embodiments (e.g., where the respective locationcorresponds to an edge of the display), the additional informationincludes a virtual desktop that was not displayed immediately prior todetecting the contact while the focus selector is at the respectivelocation (e.g., in response to detecting intensity of the contact overthe respective intensity threshold or detecting the contact for longerthan the predefined delay time while the focus selector is at the edgeof the display, switching between virtual desktops). For example, if theuser is dragging a window on a workspace or virtual desktop of anoperating system that has multiple virtual desktops, and the user dragsthe window of an application to an edge of the virtual desktop andpauses or increases the intensity of the contact over the respectiveintensity threshold while at the edge of the virtual desktop, the devicewill optionally switch from the current/first virtual desktop to adifferent/second virtual desktop that is associated with the respectiveedge of the current virtual desktop. In this example, the edge of thedisplay is associated with the virtual desktop in that a press inputwhile the focus selector is proximate to the edge of the display causesthe different virtual desktop to be displayed. In some embodiments, thedifferent virtual desktop is displayed in accordance with adetermination that a user interface object was currently selected andbeing moved in accordance with movement of the focus selector when thepress input was detected. In other words, the different virtual desktopis displayed in accordance with a determination that the user hasperformed a gesture associated with moving the user interface objectfrom the current virtual desktop to the different virtual desktop.

In some embodiments, the respective location corresponds to (3722) ahyperlink (e.g., a hyperlink in a webpage), and the additionalinformation includes content associated with the hyperlink. For example,in response to detecting intensity of the contact over the respectiveintensity threshold or detecting the contact for longer than thepredefined delay time on a hyperlink in a webpage displayed in a webbrowser, the device loads a webpage associated with the hyperlink in anew application window or the current application window of the webbrowser (e.g., immediately after detecting the increase in intensity ofthe contact or after detecting liftoff of the contact followingdetecting the increase in intensity of the contact).

While the focus selector is (3724) at the respective location: inaccordance with a determination (3726) that the contact has an intensityabove a respective intensity threshold (e.g., “IT_(D)” in FIGS. 8A-8N)before a predefined delay time has elapsed with the focus selector atthe respective location, the device displays the additional informationassociated with the respective location without waiting until thepredefined delay time has elapsed. For example, as explained withreference to FIG. 8C, while focus selector (e.g., cursor 3607-a) is atthe respective location (e.g., at scroll arrow 3606-4 in scroll bar3606-3) in accordance with a determination that contact 3605 has anintensity above a respective intensity threshold before a predefineddelay time (e.g., T_(delay)=T2−T0) has elapsed with focus selector3607-a at the respective location, the device displays the additionalinformation (e.g., additional selectable objects 3606-6 and 3606-7)associated with the respective location without waiting until thepredefined delay time has elapsed (e.g., waiting until time T2).

While the focus selector is (3724) at the respective location: inaccordance with a determination (3730) that the contact has an intensitybelow the respective intensity threshold, the device waits until thepredefined delay time has elapsed while the focus selector is at therespective location to display the additional information associatedwith the respective location. For example, as explained with referenceto FIGS. 8F-8G, while focus selector (e.g., cursor 3607-b) is at therespective location (e.g., scroll arrow 3606-4 in scroll bar 3606-3) inaccordance with a determination that contact 3608 has an intensity belowthe respective intensity threshold, the device waits until thepredefined delay time (e.g., T_(delay)=T2−T0) has elapsed while thefocus selector (e.g., cursor 3607-b) is at the respective location todisplay the additional information (e.g., additional selectable objects3606-6 and 3606-7) associated with the respective location. For example,the device waits until time T2 to display the additional informationassociated with the respective location.

In some embodiments, the device detects (3734) a tap gesture on thetouch-sensitive surface while the focus selector is at the respectivelocation. For example, the device detects a contact on the touchsensitive surface that has a duration less than a predefined maximumtap-gesture duration and/or a maximum intensity that is between aminimum contact-detection intensity (e.g., IT₀) and the respectiveintensity threshold IT_(D) (e.g., a brief, regular press gesture that isnot a “deep press” input). In some embodiments, in response to detectingthe tap gesture, the device performs (3736) an operation associated withthe user interface object (e.g., without displaying the additionalinformation associated with the respective location). In other words, insome embodiments, a regular press input (e.g., a non-deep pressinteraction) that corresponds to the user interface object performs adifferent operation from the deep press input that immediately displaysadditional information associated with the respective location (e.g.,non-deep press interaction results in navigating “back” in the browserby loading a most recent previously visited webpage in the browserrather than displaying a list of previously accessed websites).

It should be understood that the particular order in which theoperations in FIGS. 9A-9B have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,those listed in the fifth paragraph of the Description of Embodiments)are also applicable in an analogous manner to method 3700 describedabove with respect to FIGS. 9A-9B. For example, the contacts, gestures,user interface objects, intensity thresholds, and focus selectors,described above with reference to method 3700 optionally has one or moreof the characteristics of the contacts, gestures, user interfaceobjects, intensity thresholds, and focus selectors, described hereinwith reference to other methods described herein (e.g., those listed inthe fifth paragraph of the Description of Embodiments). For brevity,these details are not repeated here.

In accordance with some embodiments, FIG. 10 shows a functional blockdiagram of an electronic device 3800 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 10 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 10, an electronic device 3800 includes a display unit3802 configured to display additional information associated with arespective location; a touch sensitive surface unit 3804 configured toreceive a contact on the touch-sensitive surface unit; one or moresensor units 3805 configured to detect intensity of contacts with thetouch-sensitive surface unit 3804; and a processing unit 3806 coupled tothe display unit 3802, the touch-sensitive surface unit 3804, and thesensor units 3805. In some embodiments, the processing unit 3806includes a detecting unit 3808, a waiting unit 3810, and a displayenabling unit 3814.

The processing unit 3806 is configured to: detect a contact on thetouch-sensitive surface unit 3804 (e.g., with detecting unit 3808) whilea focus selector corresponding to the contact is at a respectivelocation on the display unit 3802 that is associated with additionalinformation that is not initially displayed on the display unit 3802;and while the focus selector is at the respective location: inaccordance with a determination that the contact has an intensity abovea respective intensity threshold before a predefined delay time haselapsed with the focus selector at the respective location, enabledisplay of the additional information (e.g., with display enabling unit3814) associated with the respective location without waiting until thepredefined delay time has elapsed; and in accordance with adetermination that the contact has an intensity below the respectiveintensity threshold, wait until the predefined delay time has elapsed(e.g., with waiting unit 3810) while the focus selector is at therespective location to enable display of the additional information(e.g., with display enabling unit 3814) associated with the respectivelocation.

In some embodiments, the processing unit 3806 is further configured toenable display of a user interface object on the display unit 3802(e.g., with display enabling unit 3814), where the user interface objectis associated with the additional information that is not initiallydisplayed on the display unit 3802; and the respective locationcorresponds to a location of the user interface object on the displayunit 3802.

In some embodiments, the additional information is information selectedfrom the group consisting of: help for the user interface object, adescription of one or more functions of the user interface object, and amenu with selectable options related to the user interface object.

In some embodiments, the processing unit 3806 is further configured todetect a tap gesture on the touch-sensitive surface unit (e.g., withdetecting unit 3808) while the focus selector is at the respectivelocation; and in response to detecting the tap gesture, perform anoperation associated with the user interface object.

In some embodiments, the user interface object is a back button; and theadditional information includes a browsing history that includes a listof representations of previously accessed information.

In some embodiments, the respective location corresponds to an edge of auser interface for navigating through an electronic document; and theadditional information includes a portion of the electronic documentthat was not displayed immediately prior to detecting the contact whilethe focus selector is at the respective location.

In some embodiments, the respective location corresponds to an edge ofthe display unit 3802; and the additional information includes a virtualdesktop that was not displayed immediately prior to detecting thecontact while the focus selector is at the respective location.

In some embodiments, the respective location corresponds to a hyperlink;and the additional information includes content associated with thehyperlink.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 9A-9B are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.10. For example, detecting operation 3702, display operations 3704 and3726, and waiting operation 3730 are, optionally, implemented by eventsorter 170, event recognizer 180, and event handler 190. Event monitor171 in event sorter 170 detects a contact on touch-sensitive display112, and event dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub-event,such as selection of an object on a user interface. When a respectivepredefined event or sub-event is detected, event recognizer 180activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 optionally utilizes or calls dataupdater 176 or object updater 177 to update the application internalstate 192. In some embodiments, event handler 190 accesses a respectiveGUI updater 178 to update what is displayed by the application.Similarly, it would be clear to a person having ordinary skill in theart how other processes can be implemented based on the componentsdepicted in FIGS. 1A-1B.

Removing an Icon from a Predefined Area

Many electronic devices have graphical user interfaces that include anapplication dock or launch bar. The application dock or launch barincludes application icons that the user may activate to launchapplications. The user may add application icons corresponding to theapplications they prefer or use often into the application dock, forquick access, and to remove application icons from the application dock.The user may also rearrange the application icons within the applicationdock. Some methods require multiple inputs for removal of theapplication icon from the application dock or sometimes result inaccidental removal of an icon from the application dock. The embodimentsdescribed below improve on these methods by allowing the user to make agesture on a touch-sensitive surface and, based on the intensity of thecontact in the gesture, move an application icon for rearrangement orremove the application icon from the application dock based on theintensity. When the user performs a gesture with a heavy contact, theuser can remove an application icon from the application dock. When theuser performs a gesture with a light contact, the application icon isretained in the application dock. The user thus has a more convenientway to remove application icons from the application dock and thelikelihood of accidental removal of icons from the application dock isreduced.

FIGS. 11A-11U illustrate exemplary user interfaces for removing an iconfrom a predefined area in accordance with some embodiments. The userinterfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIGS. 12A-12B. FIGS. 11A-11Uinclude intensity diagrams that show the current intensity of thecontact on the touch-sensitive surface relative to a plurality ofintensity thresholds including a light press intensity threshold (e.g.,“IT_(L)”) and a deep press intensity threshold (e.g., “IT_(D)”). In someembodiments, operations similar to those described below with referenceto IT_(D) are performed with reference to a different intensitythreshold (e.g., “IT_(L)”).

FIG. 11A illustrates user interface 3904 displayed on display 450 of adevice (e.g., device 300). Displayed in user interface 3904 isapplication dock or tray area 3916. One or more icons are, optionally,displayed in application dock area 3916. For example, in FIG. 11A,application icons 3906, 3908, 3910, 3912, and 3914 are displayed inapplication dock area 3916. Each application icon 3906, 3908, 3910,3912, and 3914 is associated with a respective application. For example,icon 3908 is associated with a media player or audio application. Insome embodiments, application dock or tray area 3916 is a predefinedarea displayed on display 450, where one or more application icons (suchas icon 3906, 3908, 3910, 3912, and 3914) are, optionally, placed forquick access.

Cursor 3922 is also displayed on display 450. Cursor 3922 is an exampleof a focus selector. A user optionally moves cursor 3922 on display 450(e.g., using touch-sensitive surface 451 of the device) to point at auser interface object (e.g., icons 3906, 3908, 3910, 3912, or 3914) andselect and manipulate the object with additional inputs.

FIGS. 11B-11C show a gesture detected on touch-sensitive surface 451 ofthe device while cursor 3922 is over icon 3908. The gestures isperformed with contact 3920. The gesture includes movement 3924 ofcontact 3920 across touch-sensitive surface 451, as shown in FIG. 11C.Movement 3924 corresponds to movement of cursor 3922 outside ofapplication dock area 3916; cursor 3922 moves outside of applicationdock area 3916 in accordance with movement 3924.

An intensity of contact 3920 is detected by one or more sensors in thedevice. The intensity is detected throughout the duration of thegesture. In response to detection of the gesture that includes contact3920, and in accordance with a determination by the device that contact3920 had a maximum intensity during the gesture that was below a deeppress intensity threshold (e.g., “IT_(D)”), an indication that thegesture is being performed is displayed during the gesture, and icon3908 (the icon over which cursor 3922 was located when the gesture wasdetected) is retained in application dock area 3916 after the end of thegesture. The indication is, optionally, for example, a display ofmovement of icon 3908 in accordance with movement of cursor 3922, asshown in FIG. 11C. After detecting the end of the gesture (e.g.,detecting liftoff of contact 3920 or detecting a decrease in intensityof contact 3920 from an intensity above IT_(L) to an intensity belowIT_(L)), icon 3908 is retained in application dock area 3916, as shownFIG. 11D.

In some embodiments, displaying an indication of the gesture beingperformed includes changing the appearance of icon 3908 to, e.g.,displaying ghost image 3926 of icon 3908, as shown in FIGS. 11E-11F.While ghost image 3926 is displayed, a representation of icon 3908 isdisplayed as moving in accordance with movement 3924 of contact 3920.The representation of icon 3908 that moves in accordance with movement3924 is, optionally, ghost image 3926 (as shown in FIG. 11F) orduplicate icon 3928 of icon 3908 (as shown in FIG. 11G). After the endof the gesture, icon 3908 is again displayed in application dock area3916, as shown in FIG. 11D.

In some embodiments, displaying an indication of the gesture beingperformed includes displaying movement of cursor 3922 while leaving icon3908 in place in application dock area 3916. For example, FIG. 11H showscursor 3922 moving outside of application dock area 3916 in accordancewith movement 3924 of contact 3920 while icon 3908 remains fixed at itslocation in application dock area 3916.

In some embodiments, displaying an indication of the gesture beingperformed includes displaying movement of icon 3908 during the gesturebut constraining movement of icon 3908 to application dock area 3916, asshown in FIG. 11I. In other words, icon 3908 does not move completelyoutside of application dock area 3916 (or, optionally, does not move outof application dock area 3916 at all). After the end of the gesture,icon 3908 is again displayed in application dock area 3916 at itsoriginal location, as in FIG. 11D. In some embodiments, icon 3908 ismoved to the left or right within application dock area 3916.

FIG. 11J illustrates user interface 3904, icons 3906, 3908, 3910, 3912,and 3914, application dock area 3916, and cursor 3922 displayed ondisplay 450 of the device, as in FIG. 11A. A gesture performed withcontact 3930 and movement 3934 of contact 3930 is detected ontouch-sensitive surface 451. In FIG. 11J, the device detects thatcontact 3930 reached an intensity during the gesture that was above thedeep press intensity threshold (e.g., “IT_(D)”).

In response to detection of the gesture that includes contact 3930, andin accordance with a determination by the device that contact 3930reached an intensity during the gesture that was above the deep pressintensity threshold (e.g., “IT_(D)”), icon 3908 (the icon over whichcursor 3922 was located when the gesture was detected) is moved inaccordance with movement 3934 of contact 3930, as shown in FIG. 11K, andicon 3908 is removed from application dock area 3916 after the devicedetects the end of the gesture (e.g., detecting liftoff of contact 3930or detecting a decrease in intensity of contact 3930 below IT_(L)), asshown in FIG. 11M. Icon 3908 that is removed from application dock area3916 is, optionally, displayed outside of application dock area 3916 ordeleted. In some embodiments, while icon 3908 is moved, an indicationthat icon 3908 will be removed from application dock area 3916 isdisplayed prior to the actual removal. The indication is, optionally,icon 3936 taking the place of icon 3908 in application dock area 3916,as shown in FIG. 11L.

FIG. 11N shows a gesture performed with contact 3938 detected ontouch-sensitive surface 451 while cursor 3922 is located over icon 3908.The gesture performed with contact 3938 is, optionally, a tap gesture ora press input (or stationary press input) including an increase andsubsequent decrease in intensity of a contact above a light pressintensity threshold (e.g., “IT_(L)”). In response to detection thegesture performed with contact 3938 in FIG. 11N, an applicationcorresponding to icon 3908 (FIG. 11N) is launched, as shown in FIG. 11O.

FIGS. 11P-11U illustrate an example of the user interfaces describedabove with reference to FIGS. 11A-11O implemented on a touch screen 112of a device (e.g., device 100). FIG. 11P illustrates user interface 3944displayed on touch-sensitive display 112 of a device. Displayed in userinterface 3944 is application dock or tray area 3916. One or more iconsare, optionally, displayed in application dock area 3916. For example,in FIG. 11P, application icons 3906, 3908, 3910, 3912, and 3914 aredisplayed in application dock area 3916.

FIGS. 11P-11Q show a gesture detected on touch-sensitive display 112 ofthe device. The gestures is performed with contact 3946 detected on icon3908. The gesture includes movement 3948 of contact 3946 acrosstouch-sensitive display 112, as shown in FIG. 11Q. Movement 3948includes movement outside of application dock area 3916.

An intensity of contact 3946 is detected by one or more sensors in thedevice. The intensity is detected throughout the duration of thegesture. In response to detection of the gesture that includes contact3946, and in accordance with a determination by the device that contact3946 had a maximum intensity during the gesture that was below a deeppress intensity threshold (e.g., “IT_(D)”), an indication that thegesture is being performed is displayed during the gesture, and icon3908 (the icon on which contact 3946 was detected when the gesture wasdetected) is retained in application dock area 3916 after the end of thegesture. The indication is, optionally, for example, a display ofmovement of icon 3908 in accordance with movement 3948, as shown in FIG.11Q. After the end of the gesture (e.g., detecting liftoff of contact3946 or detecting a decrease in intensity of contact 3946 from anintensity above IT_(L) to an intensity below IT_(L)), icon 3908 isretained in application dock area 3916, as shown FIG. 11R.

FIGS. 11S-11T show a gesture detected on touch-sensitive display 112 ofthe device. The gestures is performed with contact 3950 detected on icon3908. The gesture includes movement 3952 of contact 3950 acrosstouch-sensitive display 112, as shown in FIG. 11T. Movement 3952includes movement outside of application dock area 3916.

An intensity of contact 3950 is detected by one or more sensors in thedevice. The intensity is detected throughout the duration of thegesture. In response to detection of the gesture that includes contact3950, and in accordance with a determination by the device that contact3950 reached an intensity during the gesture that was above the deeppress intensity threshold (e.g., “IT_(D)”), icon 3908 (the icon on whichcontact 3950 was located when the gesture was detected) is moved inaccordance with movement 3952 of contact 3950, as shown in FIG. 11T, andicon 3908 is removed from application dock area 3916 after the end ofthe gesture, as shown in FIG. 11U.

FIGS. 12A-12B are flow diagrams illustrating a method 4000 of removingan icon from a predefined area in accordance with some embodiments. Themethod 4000 is performed at an electronic device (e.g., device 300, FIG.3, or portable multifunction device 100, FIG. 1A) with a display and atouch-sensitive surface. In some embodiments, the display is a touchscreen display and the touch-sensitive surface is on the display. Insome embodiments, the display is separate from the touch-sensitivesurface. Some operations in method 4000 are, optionally, combined and/orthe order of some operations is, optionally, changed.

As described below, the method 4000 provides an intuitive way to removean icon from a predefined area. The method reduces the cognitive burdenon a user when removing an icon from a predefined area, thereby creatinga more efficient human-machine interface. For battery-operatedelectronic devices, enabling a user to remove an icon from a predefinedarea faster and more efficiently conserves power and increases the timebetween battery charges.

The device displays a plurality of icons in a predefined area (e.g., anapplication dock or quick launch tray) on the display, where theplurality of icons include (4002) a respective icon. For example, inFIG. 11A or FIG. 11P, icons 3906, 3908, 3910, 3912, and 3914 aredisplayed in application dock area 3916.

The device detects a gesture that includes (4004) a contact (e.g., afinger contact) on the touch-sensitive surface while a focus selector isover the respective icon and subsequent movement of the contact acrossthe touch-sensitive surface that corresponds to movement of the focusselector outside of the predefined area. FIGS. 11B-11C, for example,show a gesture that includes contact 3920 and movement 3924 of contact3920 detected on touch-sensitive surface 451. The gesture is detectedwhile cursor 3922 is located over icon 3908. Movement 3924 correspondsto movement of cursor 3922 outside of application dock area 3916. Asanother example, FIGS. 11J-11K show a gesture that includes contact 3930and movement 3934 of contact 3930 detected on touch-sensitive surface451. The gesture is detected while cursor 3922 is located over icon3908. Movement 3934 corresponds to movement of cursor 3922 outside ofapplication dock area 3916.

As further examples, FIGS. 11P-11Q show a gesture that includes contact3946 and movement 3948 of contact 3946 detected on touch-sensitivedisplay 112. Contact 3946 is detected over icon 3908, and movement 3948includes movement of contact 3946 outside of application dock area 3916.FIGS. 11S-11T show a gesture that includes contact 3950 and movement3952 of contact 3950 detected on touch-sensitive display 112. Contact3950 is detected over icon 3908, and movement 3952 includes movement ofcontact 3950 outside of application dock area 3916. In these examples,the position of the contact (contact 3946 or 3950) is the analogue ofthe position of the focus selector.

In response (4006) to detecting the gesture, and in accordance with adetermination (4008) that the contact had a maximum intensity during thegesture that was below a respective intensity threshold, the devicedisplays (4010) an indication that the gesture is being performed duringthe gesture (e.g., display movement of the respective icon or a ghostimage of the respective icon), and retains (4018) the respective icon inthe predefined area after the gesture has ended (e.g., the respectiveicon bounces back or otherwise returns to its original location, orceases movement at a boundary of the predefined area, in response todetecting lift off of the contact). In response to detection of thegesture performed with contact 3920 and in accordance with adetermination that contact 3920 had a maximum intensity during thegesture that was below a defined intensity threshold, the devicedisplays, for example, movement of icon 3908 (FIG. 11C) or ghost image3926 (FIG. 11F) or duplicate icon 3928 (FIG. 11G) in accordance withmovement 3924 of contact 3920, and retains icon 3908 in application dockarea 3916 after the end of the gesture, as shown in FIG. 11D. As anotherexample, in response to detection of the gesture performed with contact3946 (FIG. 11P), icon 3908 is moved in accordance with movement 3948 ofcontact 3946 and then retained in application dock area 3916 after theend of the gesture, as shown in FIG. 11R.

In some embodiments, displaying the indication that the gesture is beingperformed includes (4012) changing the appearance of the respective iconin the predefined area (e.g., replacing the respective icon with a ghostimage of the icon) and, while displaying the respective icon with thechanged appearance on the display, moving a representation of therespective icon in accordance with movement of the contact during thegesture. For example, in response to detection of the gesture performedwith contact 3920, icon 3908 is, optionally, changed to ghost image 3926and, while ghost image 3926 is displayed, a representation of icon 3908(e.g., duplicate icon 3928 or ghost image 3926) is moved in accordancewith movement 3924, as shown in FIGS. 11E-11G.

In some embodiments, displaying the indication that the gesture is beingperformed includes (4014), while maintaining the respective icon in afixed location in the predefined area, moving a cursor on the display inaccordance with movement of the contact (e.g., unless the user presseshard enough, the icons in the dock are stationary or “stuck” in place).For example, in response to detection of the gesture performed withcontact 3920, cursor 3922 is, optionally, moved in accordance withmovement 3924 while icon 3908 remains in place, as shown in FIG. 11H.

In some embodiments, displaying the indication that the gesture is beingperformed includes (4016), while constraining movement of the respectiveicon to the predefined area, moving the respective icon in accordancewith the movement of the contact during the gesture (e.g., the icon canstill be repositioned within the dock during the gesture but cannot bemoved outside of the dock unless the user presses harder). In someembodiments, if the icon is constrained to the predefined area, the iconmoves along an edge of the predefined area that is closest to thecontact. For example, if the predefined area is horizontal strip nearthe bottom edge of the display and the focus selector is above thepredefined area, movement of the icon would track horizontal movement ofthe contact but would not track vertical movement of the contact unlessthe focus selector moved into the predefined area. For example, movementof icon 3908 in accordance with movement 3924 of contact 3920 is,optionally, constrained to within application dock area 3916, as shownin FIG. 11I.

In response (4006) to detecting the gesture, and in accordance with adetermination (4020) that the contact reached an intensity during thegesture that was above the respective intensity threshold, the devicemoves (4022) the respective icon in accordance with the movement of thecontact during the gesture (e.g., moving the respective icon outside ofthe predefined area during the gesture so that it follows the movementof the contact), and removes (4024) the respective icon from thepredefined area after the gesture has ended (e.g., deleting the icon ormoving the icon to a location outside of the predefined area in responseto detecting liftoff of the contact). For example in FIGS. 11J-11K, inresponse to detection of the gesture performed with contact 3930 and inaccordance with a determination that contact 3930 reached an intensityduring the gesture that was above the defined intensity threshold, thedevice displays, for example, movement of icon 3908 in accordance withmovement 3934 of contact 3930, and icon 3908 is removed from applicationdock area 3916 after the end of the gesture, as shown in FIG. 11M. Asanother example, in FIGS. 11S-11T, in response to detection of thegesture performed with contact 3950, icon 3908 is moved in accordancewith movement 3952 of contact 3950 and then removed from applicationdock area 3916 after the end of the gesture, as shown in FIG. 11U.

In some embodiments, prior to detecting an end of the gesture, inaccordance with a determination that the contact reached an intensityduring the gesture that was above the respective intensity threshold,prior to removing the respective icon from the predefined area, thedevice displays (4026) a visual indication that the respective icon willbe removed from dock (e.g., prior to detecting an end of the gesture,display the respective icon moving out of the predefined area and/ordisplay an icon removal symbol such as a “cloud” or a red “X” insituations where the respective icon would be permanently removed fromthe predefined area). FIG. 11L shows, for example, prior to the end ofthe gesture performed with contact 3930, icon 3936 (e.g., an applicationicon deletion indication) is displayed in application dock area 3916where icon 3908 was located.

In some embodiments, the device detects (4028) a tap gesture on thetouch-sensitive surface while the focus selector is over the respectiveicon, and in response to detecting the tap gesture, the device launches(4030) a respective application associated with the respective icon. Insome embodiments, the respective icon is a document icon that opens aparticular document with a default application. In some embodiments, therespective icon is an application icon that opens an application with nodocument or a default/blank document initially displayed. For example,in FIGS. 11N-11O, in response to detection of tap gesture 3938 ontouch-sensitive surface 451 while cursor 3922 is over icon 3908, anapplication associated with icon 3908 is launched and the correspondinginterface 3940 is displayed.

In some embodiments, instead of determining whether or not to remove therespective icon from the predefined area based on whether or not thecontact has a maximum intensity that is above or below the respectiveintensity threshold during a gesture that corresponds to movementoutside of the predefined area, the device determines whether or not torearrange a plurality of icons in the predefined area based on whetheror not the contact has a maximum intensity that is above or below therespective intensity threshold. Thus, in some embodiments, the devicedisplays a plurality of icons in a predefined area on the display,wherein the plurality of icons include a respective icon. The devicedetects a gesture that includes a contact on the touch-sensitive surfacewhile a focus selector is over the respective icon; and subsequentmovement of the contact across the touch-sensitive surface thatcorresponds to movement of the focus selector within the predefinedarea. In response to detecting the gesture: in accordance with adetermination that the contact had a maximum intensity during thegesture that was below a respective intensity threshold, the devicedisplays an indication that the gesture is being performed during thegesture; and does not rearrange (e.g., reorder) the respective icon inthe predefined area after the gesture has ended. In contrast, inaccordance with a determination that the contact reached an intensityduring the gesture that was above the respective intensity threshold,the device moves the respective icon in accordance with the movement ofthe contact during the gesture; and rearranges (e.g., reorders) therespective icon relative to other icons in the plurality of icons in thepredefined area after the gesture has ended. For example, in FIG. 11P,if the device detected movement of contact 3946, with a maximumintensity below IT_(D), to a position between icon 3910 and icon 3912,when the intensity of contact dropped below IT_(L), icon 3908 wouldreturn to its original position and the icons in predefined area 3916would not be rearranged as shown in FIG. 11R (e.g., because contact 3946had a maximum intensity below IT_(D)). In contrast, in FIG. 11S, if thedevice detected movement of contact 3950, with a maximum intensity aboveIT_(D), to a position between icon 3910 and icon 3912, when theintensity of contact dropped below IT_(L), icon 3908 would be placebetween icon 3910 and icon 3912 and the icons in predefined area 3916would accordingly be rearranged (e.g., because contact 3950 has amaximum intensity above IT_(D)). Unintentionally rearranging icons in apredefined area can be frustrating for users who may not realize thatthe icons have been rearranged and then have difficulty finding iconsthat have moved from their usual locations. Using a higher intensitythreshold (e.g., IT_(D)) to control whether user gestures rearrangeicons in the predefined area helps to prevent users from unintentionallyrearranging icons within the predefined area thereby improving theefficiency and predictability of the user interface.

It should be understood that the particular order in which theoperations in FIGS. 12A-12B have been described is merely exemplary andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,those listed in the fifth paragraph of the Description of Embodiments)are also applicable in an analogous manner to method 4000 describedabove with respect to FIGS. 12A-12B. For example, the contacts,gestures, user interface objects, intensity thresholds, and focusselectors described above with reference to method 4000 optionally hasone or more of the characteristics of the contacts, gestures, userinterface objects, intensity thresholds, and focus selectors describedherein with reference to other methods described herein (e.g., thoselisted in the fifth paragraph of the Description of Embodiments). Forbrevity, these details are not repeated here.

In accordance with some embodiments, FIG. 13 shows a functional blockdiagram of an electronic device 4100 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 13 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 13, an electronic device 4100 includes a display unit4102 configured to display a plurality of icons in a predefined area onthe display unit 4102, wherein the plurality of icons include arespective icon; a touch-sensitive surface unit 4104 configured toreceive gestures; one or more sensor units 4105 configured to detectintensity of contacts with the touch-sensitive surface unit 4104; and aprocessing unit 4106 coupled to the display unit 4102, thetouch-sensitive surface unit 4104, and the sensor units 4105. In someembodiments, the processing unit 4106 includes a detecting unit 4108, adisplay enabling unit 4110, a retaining unit 4112, a moving unit 4114, aremoving unit 4116, and a launching unit 4118.

The processing unit 4106 is configured to: detect a gesture thatincludes a contact on the touch-sensitive surface unit 4104 while afocus selector is over the respective icon and subsequent movement ofthe contact across the touch-sensitive surface unit 4104 thatcorresponds to movement of the focus selector outside of the predefinedarea (e.g., with the detecting unit 4108), and in response to detectingthe gesture: in accordance with a determination that the contact had amaximum intensity during the gesture that was below a respectiveintensity threshold, enable display of an indication that the gesture isbeing performed during the gesture (e.g., with the display enabling unit4110) and retain the respective icon in the predefined area after thegesture has ended (e.g., with the retaining unit 4112); and inaccordance with a determination that the contact reached an intensityduring the gesture that was above the respective intensity threshold,move the respective icon in accordance with the movement of the contactduring the gesture (e.g., with the moving unit 4114) and remove therespective icon from the predefined area after the gesture has ended(e.g., with the removing unit 4116).

In some embodiments, displaying the indication that the gesture is beingperformed includes: changing the appearance of the respective icon inthe predefined area, and while displaying the respective icon with thechanged appearance on the display unit 4102, moving a representation ofthe respective icon in accordance with movement of the contact duringthe gesture.

In some embodiments, displaying the indication that the gesture is beingperformed includes, while maintaining the respective icon in a fixedlocation in the predefined area, moving a cursor on the display unit4102 in accordance with movement of the contact.

In some embodiments, displaying the indication that the gesture is beingperformed includes, while constraining movement of the respective iconto the predefined area, moving the respective icon in accordance withthe movement of the contact during the gesture.

In some embodiments, the processing unit 4106 is configured to: detect atap gesture on the touch-sensitive surface unit 4104 while the focusselector is over the respective icon (e.g., with the detecting unit4108), and in response to detecting the tap gesture, launch a respectiveapplication associated with the respective icon (e.g., with thelaunching unit 4118).

In some embodiments, the processing unit 4106 is configured to: prior todetecting an end of the gesture, in accordance with a determination thatthe contact reached an intensity during the gesture that was above therespective intensity threshold, prior to removing the respective iconfrom the predefined area, enable display of a visual indication that therespective icon will be removed from dock (e.g., with the displayenabling unit 4110).

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 12A-12B are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.13. For example, detection operation 4004, displaying operation 4010,retaining operation 4018, moving operation 4022, and removing operation4024 are, optionally, implemented by event sorter 170, event recognizer180, and event handler 190. Event monitor 171 in event sorter 170detects a contact on touch-sensitive display 112, and event dispatchermodule 174 delivers the event information to application 136-1. Arespective event recognizer 180 of application 136-1 compares the eventinformation to respective event definitions 186, and determines whethera first contact at a first location on the touch-sensitive surface (orwhether rotation of the device) corresponds to a predefined event orsub-event, such as selection of an object on a user interface, orrotation of the device from one orientation to another. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 optionally utilizes or calls dataupdater 176 or object updater 177 to update the application internalstate 192. In some embodiments, event handler 190 accesses a respectiveGUI updater 178 to update what is displayed by the application.Similarly, it would be clear to a person having ordinary skill in theart how other processes can be implemented based on the componentsdepicted in FIGS. 1A-1B.

Displaying Content Layers

Many electronic devices include applications or user interfaces wheredifferent corresponding content, such as layers of content, can bedisplayed. For example, the corresponding content can be images of alocation at different times, or different types of maps for a location.In some methods, in order to display a different content layer, the userhas to open a menu and choose the desired content layer, which can betedious and time-consuming. The embodiments described below improve onthese methods. The user increases the intensity of a contact on atouch-sensitive surface while a focus selector is located over a contentlayer. If the intensity is increased above a threshold, a correspondingportion of a different content layer is displayed. The different contentlayer can also be brought up gradually in accordance with the contactintensity, or panned by moving a focus selector. These features make thedisplaying and manipulation of content layers more efficient.

FIGS. 14A-14L illustrate exemplary user interfaces for displayingcontent layers in accordance with some embodiments. The user interfacesin these figures are used to illustrate the processes described below,including the processes in FIGS. 15A-15C. FIGS. 14A-14L includeintensity diagrams that show the current intensity of the contact on thetouch-sensitive surface relative to a plurality of intensity thresholdsincluding a light press intensity threshold (e.g., “IT_(L)”) and atransition-initiation intensity threshold (e.g., “IT₁”). In someembodiments, operations similar to those described below with referenceto “IT_(L)” are performed with reference to a different intensitythreshold (e.g., “IT_(D)”).

In some embodiments, the device is an electronic device with a separatedisplay (e.g., display 450) and a separate touch-sensitive surface(e.g., touch-sensitive surface 451). In some embodiments, the device isportable multifunction device 100, the display is touch-sensitivedisplay system 112, and the touch-sensitive surface includes tactileoutput generators 167 on the display (FIG. 1A). For convenience ofexplanation, the embodiments described with reference to FIGS. 14A-14Land 15A-15C will be discussed with reference to display 450 and aseparate touch-sensitive surface 451, however analogous operations are,optionally, performed on a device with a touch-sensitive display system112 in response to detecting the contacts described in FIGS. 14A-14L onthe touch-sensitive display system 112 while displaying the userinterfaces shown in FIGS. 14A-14L on the touch-sensitive display system112; in such embodiments, the focus selector is, optionally: arespective contact, a representative point corresponding to a contact(e.g., a centroid of a respective contact or a point associated with arespective contact), or a centroid of two or more contacts detected onthe touch-sensitive display system 112, in place of cursor 6904.

FIG. 14A illustrates the device displaying content 6902 on display 450.In some embodiments, content 6902 is an image of a location (e.g.,overhead or satellite image of the location) at a first time (e.g., at aparticular date and time). In some other embodiments, content 6902 is amap, of a first type (e.g., a street map), of a location.

The device also displays a focus selector (e.g., cursor 6904) on display450. In some embodiments, cursor 6904 is a pointer (e.g., a mousepointer). In FIG. 14A, cursor 6904 is located at location 6904-a overcontent 6902. Cursor 6904 is associated with a portion of content 6902over which cursor 6904 is located. For example, in FIG. 14A, cursor6904, at location 6904-a, is associated with portion 6902-1. As cursor6904 is moved across content 6902, the associated portion of content6902 also changes with the location of cursor 6904 (e.g., the portion ofcontent 6902 associated with the focus selector corresponds to contentwithin a predefined radius or distance of cursor 6904 or within apredefined area centered at cursor 6904).

While the portion of content with which cursor 6904 is associated has afinite size, the extent (e.g., size and boundaries) of that portion isnot displayed to the user, and thus the delineation of the portion fromthe rest of content 6902 is, optionally, not apparent to the user untilthe device begins to replace the portion of the first content with acorresponding portion of second content, as described below. Forexample, in FIG. 14A, the boundaries of portion 6902-1 are not displayedon display 450 to the user.

In FIG. 14A, the device detects contact 6906 on touch-sensitive surface451 while cursor 6904 is located over portion 6902-1. The device detectsan increase in the intensity of contact 6906, from below a light pressintensity threshold (e.g., IT_(L)) to above the light press intensitythreshold (e.g., IT_(L)), while cursor 6904 is located over portion6902-1, as shown in FIGS. 14B-14C. In response to detecting the increasein the intensity of contact 6906 (e.g., from an intensity below IT_(L)in FIG. 14B to an intensity above the IT_(L) in FIG. 14C), the deviceceases to display portion 6902-1 and displays portion 6908-1 of content6908, as shown in FIG. 14C. Portion 6908-1 has the same size andposition as portion 6902-1. In FIG. 14C, content 6908 is not displayedin its entirety; just portion 6908-1 is displayed. In some embodiments,portion 6908-1 is displayed to give a visual appearance of being viewedthrough a virtual loupe or viewport, as though the user is lookingthrough a hole in content 6902 at content 6908 that is “underneath”content 6902.

In some embodiments where content 6902 is an image of a location at afirst time, content 6908 is an image of the same location at a secondtime different from the first time (e.g., a different time and date). Insome embodiments where content 6902 is a map of a first type of alocation, content 6908 is a map, of a second type different from thefirst type (e.g., public transit map), of the same location. Portions ofcontent 6908 are correlated with corresponding portions of content 6902.Thus, portion 6908-1 corresponds to portion 6902-1. For example, ifcontent 6902 and 6908 are different types of maps for the same location,then portions 6902-1 and 6908-1 are portions of the respective maps forthe vicinity of the same street intersection. In some embodiments,content 6902 is a first image and content 6908 is a second image thatcorresponds to the first image (e.g., an image of the same object or setof objects that differs from the first image based on media-capturesettings such as exposure, white balance, focus, etc., or based on imagecapture conditions such as time of day, lighting, etc.). In someembodiments, content 6902 is a first document and content 6908 is anearlier version of the first document (e.g., an earlier version of aword processing, spreadsheet, presentation, or PDF document). Whilenumerous examples have been provided, these examples are not limiting,and analogous operations are optionally performed on any set of firstcontent and second content for which it is advantageous to replace aparticular portion of the first content with the second content whilecontinuing to display other portions of the first content.

In some embodiments, in response to detecting a decrease in theintensity of contact 6906 below the light press intensity threshold(e.g., IT_(L)), content 6908-1 ceases to be displayed, and content6902-1 is re-displayed as part of content 6902 as a whole (e.g., ifcontact 6906 drops back down to the intensity shown in FIG. 14B that isbelow IT_(L), the first portion 6908-1 of the second content ceases tobe displayed).

In FIG. 14C, portion 6908-1 has a first size that is the same as thesize of portion 6902-1 in FIGS. 14A-14B. In some embodiments, that firstsize is based on the intensity of contact 6906 (e.g., as the intensityof contact 6906 increases above a predefined intensity threshold, thesize of the area of the first content 6902 that is replaced with thesecond content 6908 is increased in a corresponding manner). In responseto detecting an increase in the intensity of contact 6906, the deviceincreases the size of portion 6902-1 to a second size. If the intensityincrease is detected while portion 6908-1 is displayed, then the size ofportion 6908-1 is increased to the second size, to match the increase inthe size of portion 6902-1.

For example, FIG. 14D shows the intensity of contact 6906 increasedabove the intensity shown in FIG. 14C. The sizes of portion 6902-1 andportion 6908-1 are increased in response to detection of the intensityincrease by an amount corresponding to the amount of increase inintensity of contact 6906. The size increase for portion 6908-1 isdisplayed on display 450, but the size increase for portion 6902-1 isdisplayed as the size of the hole in content 6902 in FIG. 14D.Similarly, FIG. 14E shows the intensity of contact 6906 increased abovethe intensity shown in FIG. 14D. The sizes of portion 6902-1 and portion6908-1 are further increased, from the size shown in FIG. 14D, inresponse to detection of the intensity increase. Again, the sizeincrease for portion 6908-1 is displayed on display 450, but the sizeincrease for portion 6902-1 is displayed as the size of the hole incontent 6902 in FIG. 14E. In some embodiments, the sizes of portion6902-1 and 6908-1 are decreased in response to a decrease in theintensity of contact 6906 (e.g., the device reverses of the sizeincrease that was performed in response to the intensity increase shownin FIGS. 14C-14E).

FIG. 14F illustrates content 6902, including portion 6902-1, and cursor6904 displayed on display 450, as in FIG. 14A. The device detectscontact 6910, on touch-sensitive surface 451, with an intensity belowthe light press intensity threshold (e.g., IT_(L)) and below atransition-initiation intensity threshold (e.g., IT₁). In FIGS. 14A-14L,the transition-initiation intensity threshold (e.g., IT₁) is below thelight press intensity threshold (e.g., IT_(L)).

The device detects an increase in the intensity of contact 6910 to ahigher intensity that is still below the transition-initiation intensitythreshold (e.g., IT₁), as shown in FIG. 14G. In accordance with adetermination that the new intensity is below the transition-initiationintensity threshold (e.g., IT₁), portion 6902-1 continues to bedisplayed without displaying portion 6908-1.

In FIG. 14H, the device detects a further increase in the intensity ofcontact 6910 to an intensity above the transition-initiation intensitythreshold (e.g., IT₁) and below the light press intensity threshold(e.g., IT_(L)). In accordance with a determination that the newintensity is above the transition-initiation intensity threshold (andbelow the light press intensity threshold IT_(L)), portion 6908-1 isdisplayed, and a reduced opacity (e.g., more visually transparent)version of portion 6902-1 is displayed as overlaid over portion 6908-1.Thus, from the user's perspective, both portion 6908-1 and portion6902-1 can be seen, with portion 6908-1 being seen through amore-transparent portion 6902-1.

In some embodiments, the opacity of reduced-opacity portion 6902-1 isbased on the intensity of contact 6910 between the transition-initiationintensity threshold (e.g., IT₁) and the light press intensity threshold(e.g., IT_(L)). The opacity is reduced in response to an increase in theintensity of contact 6910, and the opacity is increased in response to adecrease in the intensity of contact 6910. Thus, portion 6908-1,optionally, has an appearance of being gradually revealed and graduallyreplacing portion 6902-1 on display 450.

In FIG. 14I, the device detects an increase in the intensity of contact6910 above the light press intensity threshold (e.g., IT_(L)). Inresponse to detecting the increase in the intensity of contact 6910above the light press intensity threshold (e.g., IT_(L)), the deviceceases to display portion 6902-1 (reduced-opacity or otherwise) anddisplays content portion 6908-1. While the foregoing example of thefirst portion of the first content 6902 gradually ceasing to bedisplayed has been described with reference to transition-initiationthreshold IT₁ and light press intensity threshold IT_(L), in someembodiments, IT_(L) is the intensity threshold at which the firstportion of the first content 6902 starts to gradually disappear toreveal the first portion of the second content 6908, and the deep pressintensity threshold IT_(D) is the intensity threshold at which the firstportion of the first content completely disappears to reveal the firstportion of the second content 6908.

FIG. 14J shows cursor 6904 located at location 6904-1, over portion6908-1, and contact 6910 located at location 6910-a. As shown in FIGS.14J-14L the device detects, on touch-sensitive surface 451, movement6912 of contact 6910 from location 6910-a toward location 6910-b (FIGS.14K-14L). In response to detection of the movement of contact 6926,cursor 6904 is moved from location 6904-a (FIG. 14J) to location 6904-b(FIGS. 14K-14L, over portion 6902-2 of content 6902, as shown in FIG.14K. The device ceases to display portion 6902-2 and displays portion6908-2, which corresponds to portion 6902-2, as shown in FIG. 14L.

In FIGS. 14J-14L, cursor 6904 moves in response to movement 6912 ofcontact 6910, a portion of content 6908 is still displayed and thedisplayed portion of content 6908 changes as cursor 6904 moves over anew portion of content 6902; the displayed portion of content 6908follows cursor 6904. For example, if the portion of content 6908 isdisplayed as if viewed through a virtual loupe, viewport or hole incontent 6902, the virtual loupe, viewport or hole in content 6902 ismoved along with cursor 6904 and the portion of content 6908 viewedthrough the virtual loupe or viewport changes. In FIG. 14K, for ease ofunderstanding of the movement of cursor 6904 over a different portion ofcontent 6902, the displayed portion of content 6908 is not shown.Further, as shown in FIG. 14K, portions 6902-1 and 6902-2, optionally,overlap at least partially.

FIGS. 15A-15C are flow diagrams illustrating a method 7000 of displayingcontent layers in accordance with some embodiments. The method 7000 isperformed at an electronic device (e.g., device 300, FIG. 3, or portablemultifunction device 100, FIG. 1A) with a display and a touch-sensitivesurface. In some embodiments, the display is a touch screen display andthe touch-sensitive surface is on the display. In some embodiments, thedisplay is separate from the touch-sensitive surface. Some operations inmethod 7000 are, optionally, combined and/or the order of someoperations is, optionally, changed.

As described below, the method 7000 provides an intuitive way to displaycontent layers. The method reduces the cognitive burden on a user whendisplaying content layers, thereby creating a more efficienthuman-machine interface. For battery-operated electronic devices,enabling a user to display content layers faster and more efficientlyconserves power and increases the time between battery charges.

The device displays (7002), on the display, first content, whereportions of the first content are correlated with corresponding portionsof second content that are not (initially) displayed on the display(e.g., the corresponding portions of the second content are notdisplayed prior to detecting the increase in intensity of the contact onthe touch-sensitive surface, as described below). For example, FIGS. 14Aand 14F show content 6902 being displayed on display 450, where portionsof content 6902 are correlated with corresponding portions of content6908, which is not initially displayed.

While a focus selector is over a first portion of the first content, thedevice detects (7014) an increase in intensity of a contact on thetouch-sensitive surface above a respective intensity threshold (e.g.,IT_(L)). For example, FIGS. 14A-14B show the detection of an increase inthe intensity of contact 6906 above the respective intensity threshold(e.g., IT_(L)), while cursor 6904 is located over portion 6902-1. FIGS.14G-14I show the detection of an increase in the intensity of contact6910 above the respective intensity threshold (e.g., IT_(L)), whilecursor 6904 is located over portion 6902-1.

In response to detecting (7018) the increase in intensity of the contacton the touch-sensitive surface above the respective intensity threshold(e.g., IT_(L)), the device ceases (7020) to display the first portion ofthe first content, and displays (7022) a first portion of the secondcontent that corresponds to the first portion of the first content. Forexample, in FIGS. 14A-14C, in response to detecting the increase in theintensity of contact 6906 above the respective intensity threshold(e.g., IT_(L)), the device ceases to display portion 6902-1 (FIGS. 14Aand 14B) and displays portion 6908-1 (FIG. 14C), which corresponds toportion 6902-1. In FIGS. 14G-14I, in response to detecting the increasein the intensity of contact 6910 above the respective intensitythreshold (e.g., IT_(L)), the device ceases to display portion 6902-1(FIG. 14G) and displays portion 6908-1 (FIG. 14I).

In some embodiments, prior to displaying the first portion of the secondcontent (7004), the device detects (7006) an increase in intensity ofthe contact from a first intensity below the respective intensitythreshold (e.g., IT_(L)) to a second intensity below the respectiveintensity threshold (e.g., IT_(L)). In response to detecting (7008) theincrease in intensity of the contact to the second intensity below therespective intensity threshold (e.g., IT_(L)), in accordance with adetermination that the second intensity is below a transition-initiationintensity threshold (e.g., IT₁), the device continues (7010) to displaythe first portion of the first content without displaying the firstportion of the second content; and in accordance with a determinationthat the intensity of the contact is above the transition-initiationintensity threshold (e.g., IT₁), the device displays (7012) a reducedopacity version of the first portion of the first content overlaid overthe first portion of the second content. In some embodiments, theopacity of the first portion of the first content decreases withincreasing intensity up to the respective threshold. As shown in FIGS.14F-14G, for example, prior to displaying portion 6908-1, the devicedetects an increase in the intensity of contact 6910 to intensitiesbelow the respective intensity threshold (e.g., IT_(L)). In accordancewith a determination that the new intensity is below thetransition-initiation intensity threshold IT₁, as shown in FIG. 14G, thedevice continues to display portion 6902-1, without displaying portion6908-1. In contrast, in accordance with a determination that the newintensity is above the transition-initiation intensity threshold IT₁, asshown in FIG. 14H, the device displays a reduced-opacity version ofportion 6902-1 overlaid over portion 6908-1.

In some embodiments, the size (e.g., area) of the first portion of thefirst content (and the corresponding first portion of the secondcontent) is determined (7016) based on an intensity of the contact.After displaying (7028) the first portion of the second content, thedevice detects (7030) an increase in the intensity of the contact, andin response to detecting an increase in intensity of the contact,increases (7032) the size of the first portion of the second content(and the corresponding first portion of the first content). For example,in FIGS. 14C-14E, after displaying portion 6908-1, the device detects anincrease in the intensity of contact 6906. In response to detecting theincrease in intensity, the device increases the size of portion 6902-1(in the background), and the size of portion 6908-1 to match the newsize of portion 6902-1, as shown in FIG. 14E.

In some embodiments, the first content includes (7024) an image of alocation (e.g., a physical location) at a first time, the second contentincludes an image of the location at a second time distinct from thefirst time, and the first portion of the first content and the firstportion of the second content correspond to a same portion of thelocation. For example, content 6902 includes an image of a location at afirst time, and content 6908 includes an image of the location at asecond time different from the first time. Portion 6902-1 corresponds toportion 6908-1; they show the same portion of the location at differenttimes.

In some embodiments, the first content includes (7026) a first map of alocation (e.g., a physical location), the second content includes asecond map of the location, where the first map is different from thesecond map, and the first portion of the first content and the firstportion of the second content correspond to a same portion of thelocation. For example, the first map includes different map featuresfrom the map features included in the second map (e.g., a 1902 map ofSan Francisco instead of a 2012 map of San Francisco or a street map ofSan Francisco overlaid over a public transit map of San Francisco). Forexample, content 6902 includes a map of a first type (e.g., street map)of a location, and content 6908 includes a map of a second type (e.g.,public transit map) different from the first type, of the location.Portion 6902-1 corresponds to portion 6908-1; they show different maptypes for the same portion of the location.

In some embodiments, after displaying (7028) the first portion of thesecond content, the device detects (7034) movement of the contact. Inresponse to detecting (7036) movement of the contact, the device moves(7038) the focus selector over a second portion of the first content,ceases (7040) to display the second portion of the first content, anddisplays (7042) a second portion of the second content that correspondsto the second portion of the first content (e.g., the “revealed” area ofthe second content moves in accordance with movement of the contact onthe touch-sensitive surface). For example, in FIGS. 14J-14L, afterdisplaying portion 6908-1, the device detects movement 6912 of contact6910 on touch-sensitive surface 451. In response to detecting themovement 6912 of contact 6910, the device moves cursor 6904 on display450 and then ceases to display portion 6902-2 and displays portion6908-2 which are portions of the first content 6902 and second content6908 that correspond to the new location of cursor 6904 on display 450.

In some embodiments, the second portion of the first content at leastpartially overlaps the first portion of the first content (7044). Insome embodiments, the second portion of the second content at leastpartially overlaps the first portion of the second content (e.g., the“revealed” area of the second content changes smoothly in accordancewith movement of the contact, so that as a row of pixels is revealed onthe right edge of the “revealed” area, a corresponding row of pixelsceases to be revealed on the left edge of the “revealed” area). Forexample, as shown in FIG. 14K, portions 6902-1 and 6902-2 overlap.

It should be understood that the particular order in which theoperations in FIGS. 15A-15C have been described is merely exemplary andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,those listed in the fifth paragraph of the Description of Embodiments)are also applicable in an analogous manner to method 7000 describedabove with respect to FIGS. 15A-15C. For example, the contacts,intensity thresholds, and focus selectors described above with referenceto method 7000 optionally have one or more of the characteristics of thecontacts, intensity thresholds, and focus selectors described hereinwith reference to other methods described herein (e.g., those listed inthe fifth paragraph of the Description of Embodiments). For brevity,these details are not repeated here.

In accordance with some embodiments, FIG. 16 shows a functional blockdiagram of an electronic device 7100 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 16 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 16, an electronic device 7100 includes a display unit7102 configured to display, on the display unit 7102, first content,where portions of the first content are correlated with correspondingportions of second content that are not displayed on the display unit7102; a touch-sensitive surface unit 7104 configured to receivecontacts; one or more sensors 7106 configured to detect intensity ofcontacts with the touch-sensitive surface unit 7104; and a processingunit 7108 coupled to the display unit 7102, the touch-sensitive surfaceunit 7104, and the sensors 7106. In some embodiments, the processingunit 7108 includes a detecting unit 7110, a ceasing unit 7112, a displayenabling unit 7114, an increasing unit 7116, and a moving unit 7118.

The processing unit 7108 is configured to: while a focus selector isover a first portion of the first content, detect an increase inintensity (e.g., with the detecting unit 7110) of a contact on thetouch-sensitive surface unit 7104 above a respective intensity threshold(e.g., IT_(L)) ; and in response to detecting the increase in intensityof the contact on the touch-sensitive surface unit 7104 above therespective intensity threshold: cease to display the first portion ofthe first content (e.g., with the ceasing unit 7112), and enable displayof a first portion of the second content that corresponds to the firstportion of the first content (e.g., with the display enabling unit7114).

In some embodiments, the size of the first portion of the first contentis determined based on an intensity of the contact; and the processingunit 7108 is configured to, after enabling display of the first portionof the second content: detect an increase in the intensity of thecontact (e.g., with the detecting unit 7110), and in response todetecting an increase in intensity of the contact, increase the size ofthe first portion of the second content (e.g., with the increasing unit7116).

In some embodiments, the processing unit 7108 is configured to, prior toenabling display of the first portion of the second content: detect anincrease in intensity of the contact from a first intensity below therespective intensity threshold to a second intensity below therespective intensity threshold (e.g., with the detecting unit 7110); andin response to detecting the increase in intensity of the contact to thesecond intensity below the respective intensity threshold: in accordancewith a determination that the second intensity is below atransition-initiation intensity, continue to enable display of the firstportion of the first content without enabling display of the firstportion of the second content (e.g., with the display enabling unit7114); and in accordance with a determination that the intensity of thecontact is above the transition-initiation intensity threshold (e.g.,IT₁), enable display of a reduced opacity version of the first portionof the first content overlaid over the first portion of the secondcontent (e.g., with the display enabling unit 7114).

In some embodiments, the processing unit 7108 is configured to, afterenabling display of the first portion of the second content: detectmovement of the contact (e.g., with the detecting unit 7110); and inresponse to detecting movement of the contact: move the focus selectorover a second portion of the first content (e.g., with the moving unit7118); cease to enable display of the second portion of the firstcontent (e.g., with the ceasing unit 7112); and enable display of asecond portion of the second content that corresponds to the secondportion of the first content (e.g., with the display enabling unit7114).

In some embodiments, the second portion of the first content at leastpartially overlaps the first portion of the first content.

In some embodiments, the first content includes an image of a locationat a first time, the second content includes an image of the location ata second time distinct from the first time, and the first portion of thefirst content and the first portion of the second content correspond toa same portion of the location.

In some embodiments, the first content includes a first map of alocation, the second content includes a second map of the location,where the first map is different from the second map, and the firstportion of the first content and the first portion of the second contentcorrespond to a same portion of the location.

The operations in the information processing methods described aboveare, optionally, implemented by running one or more functional modulesin information processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 15A-15C are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.16. For example, detection operation 7014, ceasing operation 7020, anddisplaying operation 7022 are, optionally, implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 detects a contact on touch-sensitive display 112, andevent dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub-event,such as selection of an object on a user interface. When a respectivepredefined event or sub-event is detected, event recognizer 180activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 optionally utilizes or calls dataupdater 176 or object updater 177 to update the application internalstate 192. In some embodiments, event handler 190 accesses a respectiveGUI updater 178 to update what is displayed by the application.Similarly, it would be clear to a person having ordinary skill in theart how other processes can be implemented based on the componentsdepicted in FIGS. 1A-1B.

Navigating Between Displayed User Interfaces

Many electronic devices include user interfaces that include differentrepresentations of a same object (e.g., content such as an email orphoto). In some situations the different representations of the sameobject are organized into a hierarchy (e.g., a conversation includingmultiple messages or a photo album including multiple photos). Suchgroupings require convenient methods for navigating between userinterfaces corresponding to levels of the hierarchy. Some methods fornavigating between user interfaces on a device with a touch-sensitivesurface typically require a user to locate an affordance (e.g., a key ora “button”). Such methods, however, are problematic because they areprone to inaccuracies (e.g., accidental selection of the affordance,accidental selection of a different key when intending to select theaffordance). Such methods also increase the cognitive burden on the userby requiring additional independent gestures. The embodiments describedbelow provide a convenient and intuitive method for navigating betweenuser interfaces corresponding to different representations of an objectusing similar gestures performed with a contact while a focus selectoris over a representation of the object. In the embodiments describedbelow, an improved method is provided for navigating between a firstuser interface that includes, at least, a first representation of anobject and a second user interface that includes, at least, a secondrepresentation of the object. While displaying the first user interface,when the device detects a gesture that meets certain navigation criteriafor the object, the device replaces the first user interface with thesecond user interface. While displaying the second user interface, whenthe device detects a gesture that meets certain navigation criteria, thedevice replaces the second user interface with the first user interface.

FIGS. 17A-17H illustrate exemplary user interfaces for navigatingbetween displayed user interfaces in accordance with some embodiments.The user interfaces in these figures are used to illustrate theprocesses described below, including the processes in FIGS. 18A-18C.FIGS. 17A-17H include intensity diagrams that show the current intensityof the contact on the touch-sensitive surface relative to a plurality ofintensity thresholds including a respective threshold (e.g., “IT_(L)”).In some embodiments, operations similar to those described below withreference to “IT_(L)” are performed with reference to a differentintensity threshold (e.g., “IT_(D)”).

In some embodiments, the device is an electronic device with a separatedisplay (e.g., display 450) and a separate touch-sensitive surface(e.g., touch-sensitive surface 451). In some embodiments, the device isportable multifunction device 100, the display is touch-sensitivedisplay system 112, and the touch-sensitive surface includes tactileoutput generators 167 on the display (FIG. 1A). For convenience ofexplanation, the embodiments described with reference to FIGS. 17A-17Hand 18A-18C will be discussed with reference to a touch screen 112,however analogous operations are, optionally, performed on a device witha display 450 and a separate touch-sensitive surface 451 in response todetecting the contacts described in FIGS. 17A-17H on the touch-sensitivesurface 451 while displaying the user interfaces shown in FIGS. 17A-17Hon the display 450; in such embodiments, the focus selector is,optionally a cursor or pointer that is displayed at a locationcorresponding to (e.g., at or near) the location of the contacts (e.g.,8406, 8410 and 8412) shown in FIGS. 17A-17H.

FIG. 17A illustrates an exemplary user interface (e.g., a first userinterface) on an electronic device 300 with a touch screen display 112,which is replaced in response to particular gestures, described below,with a second user interface, distinct from the first, that is currentlynot displayed in FIG. 17A. In some embodiments, the device displaysrepresentations of objects (e.g., media objects such as songs, pictures,and/or electronic documents). In some embodiments, some or all of theobjects are electronic messages (e.g., electronic mail messages, SMSmessages, instant messages, etc.) or groupings of messages (e.g.,conversations). In some embodiments, the device displays a list with aplurality of entries, and the entries are the representations of theobjects. The example shown in FIG. 17A illustrates a displayed list ofrepresentations of conversations (user interface objects 8404-1 through8404-4 represent, respectively, conversations 1-4). Each conversationcontains one or more messages. In some circumstances, it is desirable tochange the display shown in FIG. 17A to a different display thatincludes a list of messages within a particular conversation (e.g.,navigate from an inbox view to a conversation view). FIGS. 17A-17Hillustrate examples of improved user interfaces for navigating between,for example, these different views.

FIG. 17B illustrates detection of a contact 8406 while a focus selectoris over user interface object 8404-1. In some embodiments, contact 8406is part of a gesture that optionally includes, for example, othermovements and press inputs on the touch-sensitive surface.

In some embodiments, when navigation criteria are met, the devicedisplays a second user interface. In some embodiments, the navigationcriteria include that the gesture has a maximum intensity above therespective intensity threshold (e.g., an intensity threshold that isgreater than a nominal intensity measurement that indicates that acontact is touching the touch-sensitive surface, such as IT_(L), whichis greater than contact detection intensity threshold IT₀), as shownwith contact 8406 in FIG. 17B. In some embodiments, navigation criteriainclude that, while the focus selector (e.g., while the gesture) iscontinuously over a representation of an object, an increase inintensity is detected from below the respective intensity threshold(e.g., IT_(L)) to above the respective intensity threshold (e.g., a“down-stroke” is detected). In some embodiments, navigation criteriainclude that, while the focus selector is continuously over arepresentation of an object, a decrease in intensity is detected fromabove the respective intensity threshold (e.g., IT_(L)) to below therespective intensity threshold (e.g., a “up-stroke” is detected). Insome embodiments, navigation criteria include that, while the focusselector is continuously over a representation of an object, an increasein intensity is detected from below the respective intensity threshold(e.g., IT_(L)) to above the respective intensity threshold (e.g.,IT_(L)), and subsequently a decrease in intensity is detected from abovethe respective intensity threshold (e.g., IT_(L)) to below therespective intensity threshold (e.g., both an up-stroke and adown-stroke are detected without leaving the representation).

FIGS. 17A-17H illustrate examples in which detecting a contact having amaximum intensity above IT_(L) while the focus selector is over aparticular representation of an object is sufficient to meet thenavigation criteria. Contact 8406 therefore fulfills the criteria. Thus,contact 8406 in FIG. 17B will initiate display of the second userinterface. It will be apparent to those with skill in the art, however,that other additional and/or alternative criteria are, optionally, usedin place or in combination with the criteria described herein.

In some embodiments, the device optionally displays an animatedtransition between the first user interface and the second userinterface. FIG. 17C illustrates an example of such a transition. In theillustrated example, a first set of messages (e.g., user interfaceobject 8404-1 and 8404-3) slides out of the way in one direction, and asecond set of messages (e.g., user interface object 8404-2 and 8404-4)slides out of the way in the opposite direction, thereby revealing thesecond user interface (e.g., a conversation view) “beneath” the firstuser interface.

FIG. 17D illustrates an example of an animation in accordance withembodiments in which the animation includes visual cues indicating thata particular representation is expanding to become a correspondingdocument, message, or list of messages. FIG. 17D illustrates an exampleof a selected conversation expanding to reveal a list of messagescorresponding to the selected conversation. In some embodiments, an“expanding messages” animation, such as the animation illustrated inFIG. 17D, follows a “sliding messages” animation (e.g., such as theanimation illustrated in FIG. 17C). In some embodiments, the expandingmessages animation or the sliding message animation occur independentlyof one another. In addition, it is envisioned that any number ofpossible animations are, optionally, utilized and that differentanimations for different types of objects and/or different circumstancesare sometimes appropriate. An additional specific example of ananimation, a “trampoline” animation, is described with respect to method8500 in FIGS. 18A-18C.

FIG. 17E illustrates the result of navigating from the first userinterface, in FIG. 17B, to a second user interface. In particular, FIG.17E illustrates that the user has now navigated to a conversation view.In addition, FIG. 17E illustrates a contact 8410 that is included in agesture and meets navigation criteria.

In some embodiments, since the conversation view is an example of a userinterface that is not on either extreme of a hierarchy of userinterfaces (for example, a user could up-navigate in the hierarchy toreturn to the inbox view or down-navigate in the hierarchy to view anindividual message), the device is configured to respond separately toup-navigation criteria and down-navigation criteria. For example, insome embodiments, the up-navigation criteria include that the gestureinclude a deep press (e.g., a press input with an intensity above thedeep press intensity threshold, IT_(D)) whereas the down-navigationcriteria include that the gesture has a maximum intensity between IT_(L)and IT_(D). In some embodiments, the down-navigation criteria includethat the gesture include a deep press (e.g., a press input with anintensity above the deep press intensity threshold, IT_(D)) whereas theup-navigation criteria include that the gesture has a maximum intensitybetween IT_(L) and IT_(D). In some embodiments, other gestures,movements, gestures with multiple fingers, or a combination of light anddeep press inputs are used separately and/or in combination todistinguish between up-navigation and down-navigation inputs.

For the purposes of providing an example, it is assumed that the gesturethat includes contact 8410 in FIG. 17E is a down-navigation input. Insome embodiments, an animation is displayed that is either the same as,or different than, the animation displayed in the previously describedtransition (e.g., from the inbox view to the conversation view withreference to FIGS. 17B-17E).

FIG. 17F continues the example by illustrating that contact 8410 in FIG.17E (by virtue of meeting navigation criteria and/or up-navigationcriteria) has caused the device to respond by displaying a third userinterface (namely, a message view). FIG. 17F includes a contact 8412. Inthis example, a gesture that includes contact 8412 meets up-navigationcriteria at least by virtue of a having a maximum intensity aboveIT_(L).

FIG. 17G illustrates an example of some embodiments in which the devicedisplays an animation of a first set of messages “sliding in” from afirst direction and a second set of messages “sliding in” from a seconddirection (e.g., the opposite direction), thereby “covering up” thepreviously displayed message and returning to the second user interface(or in some cases, the first user interface).

FIG. 17H illustrates the result of up-navigating from the message viewshown in FIG. 17F. In this example, the conversation view is once againdisplayed.

FIGS. 18A-18C are flow diagrams illustrating a method 8500 of navigatingbetween displayed user interfaces in accordance with some embodiments.The method 8500 is performed at an electronic device (e.g., device 300,FIG. 3, or portable multifunction device 100, FIG. 1A) with a displayand a touch-sensitive surface. In some embodiments, the display is atouch screen display and the touch-sensitive surface is on the display.In some embodiments, the display is separate from the touch-sensitivesurface. Some operations in method 8500 are, optionally, combined and/orthe order of some operations is, optionally, changed.

As described below, the method 8500 provides an intuitive way tonavigate between displayed user interfaces. The method reduces thecognitive burden on a user when navigating between displayed userinterfaces, thereby creating a more efficient human-machine interface.For battery-operated electronic devices, enabling a user to navigatingbetween displayed user interfaces faster and more efficiently conservespower and increases the time between battery charges.

The device displays (8502) a first user interface on a display (e.g.,inbox view, FIG. 17A). While a focus selector is over a firstrepresentation of an object in the first user interface (e.g., userinterface object 8404-1, FIG. 17B), the device detects (8504) a firstgesture on a touch-sensitive surface that includes a first contact witha maximum intensity during the first gesture above a respectiveintensity threshold (e.g., contact 8406, FIG. 17B).

In some embodiments, the respective intensity threshold (e.g., IT_(L))corresponds (8506) to an intensity measurement that is greater than anominal intensity measurement (e.g., IT₀) that indicates that a contactis touching the touch-sensitive surface. In some embodiments, when theone or more sensors used to detect contact intensity (e.g., “intensitysensors”) are capable of measuring 4 or more quantized values ofintensity, where N is the lowest quantized value of intensity (e.g., thevalue of intensity that corresponds to the presence of a contact on thetouch-sensitive surface), the respective intensity threshold is at leastone level above N. For example if there are 4 quantized values ofintensity and 1 is the lowest level, then the respective intensitythreshold is 2, or a level greater than 2. As another example, if thereare 256 quantized values of intensity and 1 is the lowest level, thenthe respective intensity threshold is 2, or a level greater than 2, suchas 5, 10 or 15.

In response to detecting the first gesture, the device replaces (8508)the first user interface with a second user interface that includes asecond representation of the object (e.g., conversation view, FIG. 17Eor message view, FIG. 17F).

In some embodiments, the object is (8510) an electronic document (e.g.,a word processing document, a spreadsheet document, a presentationdocument or a PDF), the first representation is an icon that correspondsto the electronic document, and the second representation is a view ofthe electronic document (e.g., an application window for viewing and/orresponding to the electronic document, a document editing user interfacefor editing the electronic document or another interface for interactingwith the electronic document).

In some embodiments, the object is (8512) an electronic message (e.g.,an email, text message, instant message, or SMS, MMS, or a socialnetworking message), the first representation is a message list entry ina list of electronic messages (e.g., a representation of an email in aninbox, such as user interface object 8404-1, FIG. 17A), and the secondrepresentation is a view of the electronic message that corresponds tothe message list entry (e.g., message view, FIG. 17F). While many of theembodiments described herein are illustrated with the example of aconversation/message hierarchy, where the first representation of theobject is a representation of a message within a conversation and thesecond representation of the object is a view of the full message, theprinciples described herein are applicable in an analogous manner toitems in other hierarchies. In particular, the object could be anotherhierarchical item such as a discussion thread (e.g., with a firstrepresentation of a top-level discussion and a second representation ofa sub-discussion), an album (e.g., with a first representation of a songin an album view and a second expanded representation of the song), or anews story (e.g., with a first representation as a headline withassociated summary or image and a second representation with the fullnews story).

In some embodiments, the first user interface includes (8514) a listwith a plurality of entries that represent corresponding objects (forexample, the list of electronic messages described with reference tooperation 8512, or, alternatively, a list of songs in an album, etc.),where the first representation of the object is one of the entries inthe list, and replacing the first user interface with the second userinterface includes sliding a first set of one or more of the entriesaway from the first representation of the object in a first directionand sliding a second set of one or more of the entries away from thefirst representation of the object in a second direction different fromthe first direction. In some embodiments, replacing the first userinterface with the second user interface further includes displaying ananimation of the first representation (a list entry) expanding to becomethe corresponding document or message (e.g., message list expanding,FIG. 17D). In some embodiments, the first direction is to the right andthe second direction is to the left, or vice versa. In some embodiments,the first direction is up and the second direction is down, or viceversa.

While the focus selector is over the second representation of the objectin the second user interface, the device detects (8516) a second gestureon the touch-sensitive surface that includes a second contact with amaximum intensity during the second gesture above the respectiveintensity threshold (e.g., contact 8412, FIG. 17F). In response todetecting the second gesture, the device replaces (8518) the second userinterface with the first user interface (e.g., displaying theconversation view, FIG. 17G).

In some embodiments, the second gesture is (8520) a repetition of thefirst gesture (e.g., the second gesture includes the same basic movementand/or intensity change components as the first gesture, although thesecond gesture occurs at a later time).

In some embodiments, the first user interface includes (8522) a listwith a plurality of entries that represent corresponding objects, wherethe first representation of the object is one of the entries in thelist, and replacing the second user interface with the first userinterface includes sliding a first set of one or more of the entriestoward the first representation of the object in a first direction andsliding a second set of one or more of the entries toward the firstrepresentation of the object in a second direction different from thefirst direction (e.g., sliding list entries in, FIG. 17G). In someembodiments, replacing the second user interface with the first userinterface further includes displaying an animation of the document ormessage collapsing to become the corresponding first representation (alist entry).

In some embodiments, prior to replacing the first user interface withthe second user interface, the device detects (8524) an increase inintensity of the first contact above the respective intensity threshold.In response to detecting the increase in intensity of the first contact,the device displays (8526) a first animation of the first representationdistorting (e.g., stretching backwards into the display like atrampoline with a weight placed on it) in accordance with the increasein intensity of the first contact. In some embodiments, the first userinterface is replaced with the second user interface in response todetecting a decrease in intensity and/or liftoff of the first contactand includes displaying an animation of a reverse of the distortion ofthe first representation (e.g., the first representation bounces backlike a trampoline after a weight is lifted off of the trampoline). Insome embodiments, prior to replacing the second user interface with thefirst user interface, the device detects (8528) an increase in intensityof the second contact above the respective intensity threshold. Inresponse to detecting the increase in intensity of the second contact,the device displays (8530) a second animation of the secondrepresentation distorting (e.g., stretching backward into the displaylike a trampoline with a weight placed on it) in accordance with theincrease in intensity of the second contact. In some embodiments, thesecond user interface is replaced with the first user interface inresponse to detecting a decrease in intensity and/or liftoff of thesecond contact and includes displaying an animation of a reverse of thedistortion of the second representation (e.g., the second representationbounces back like a trampoline after a weight is lifted off of thetrampoline).

In some embodiments, the first animation includes (8532) adjustingdisplay of the first representation by displaying a plurality of visualcues (e.g., visual cues associated with a respective physical metaphor)in accordance with the intensity of the first contact (e.g., moving acenter of the first representation downward and showing distortion ofthe edges of the first representation to indicate that the firstrepresentation is stretching downward in accordance with the intensityof the first contact). The second animation includes adjusting displayof the second representation by displaying the plurality of visual cues(e.g., visual cues associated with the same respective physicalmetaphor) in accordance with the intensity of the second contact (e.g.,moving a center of the second representation downward and showingdistortion of the edges of the second representation to indicate thatthe second representation is stretching downward in accordance with theintensity of the second contact). In some embodiments, the firstanimation and the second animation include similar distortions ofcorresponding user interface elements displayed on the display. It isintended that many other transitions and/or animations fall within thescope of the current disclosure. For instance, several alternativeanimations are discussed herein with reference to FIGS. 17A-17H.

It should be understood that the particular order in which theoperations in FIGS. 18A-18C have been described is merely exemplary andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,those listed in the fifth paragraph of the Description of Embodiments)are also applicable in an analogous manner to method 8500 describedabove with respect to FIGS. 18A-18C. For example, the contacts,gestures, user interface objects, intensity thresholds, focus selectors,animations described above with reference to method 8500 optionally haveone or more of the characteristics of the contacts, gestures, userinterface objects, intensity thresholds, focus selectors, animationsdescribed herein with reference to other methods described herein (e.g.,those listed in the fifth paragraph of the Description of Embodiments).For brevity, these details are not repeated here.

In accordance with some embodiments, FIG. 19 shows a functional blockdiagram of an electronic device 8600 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 19 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 19, an electronic device 8600 includes a display unit8602 configured to display a first user interface that includes a firstrepresentation of an object and a second user interface that includes asecond representation of the object; a touch-sensitive surface unit 8604configured to detect while a focus selector is over the firstrepresentation of an object in the first user interface, a first gestureon the touch-sensitive surface unit that includes a first contact with amaximum intensity during the first gesture above a respective intensitythreshold, and to detect, while the focus selector is over the secondrepresentation of the object in the second user interface, a secondgesture on the touch-sensitive surface unit that includes a secondcontact with a maximum intensity during the second gesture above therespective intensity threshold; one or more sensor units 8606 configuredto detect intensity of contacts with the touch-sensitive surface unit8604; and a processing unit 8608 coupled to the display unit 8602, thetouch-sensitive surface unit 8604 and the one or more sensor units 8606.In some embodiments, the processing unit 8608 includes a replacing unit8610, an animating unit 8612, and a display enabling unit 8614.

The processing unit 8608 is configured to: in response to detecting thefirst gesture, replace (e.g., with replacing unit 8610) the first userinterface with the second user interface; and in response to detectingthe second gesture, replace the second user interface with the firstuser interface.

In some embodiments, the respective intensity threshold corresponds toan intensity measurement that is greater than a nominal intensitymeasurement that indicates that a contact is touching thetouch-sensitive surface unit 8604.

In some embodiments, the second gesture is a repetition of the firstgesture.

In some embodiments, the object is an electronic message; the firstrepresentation is a message list entry in a list of electronic messages;and the second representation is a view of the electronic message thatcorresponds to the message list entry.

In some embodiments, the object is an electronic document; the firstrepresentation is an icon that corresponds to the electronic document;and the second representation is a view of the electronic document.

In some embodiments, the first user interface includes a list with aplurality of entries that represent corresponding objects, wherein thefirst representation of the object is one of the entries in the list;and replacing the first user interface with the second user interfaceincludes: sliding a first set of one or more of the entries away fromthe first representation of the object in a first direction; and slidinga second set of one or more of the entries away from the firstrepresentation of the object in a second direction different from thefirst direction.

In some embodiments, the first user interface includes a list with aplurality of entries that represent corresponding objects, wherein thefirst representation of the object is one of the entries in the list;and replacing the second user interface with the first user interfaceincludes: sliding a first set of one or more of the entries toward thefirst representation of the object in a first direction; and sliding asecond set of one or more of the entries toward the first representationof the object in a second direction different from the first direction.

In some embodiments, the processing unit 8608 is further configured to:prior to replacing the first user interface with the second userinterface: detect an increase in intensity of the first contact abovethe respective intensity threshold; and in response to detecting theincrease in intensity of the first contact, display a first animation ofthe first representation distorting in accordance with the increase inintensity of the first contact; prior to replacing the second userinterface with the first user interface: detect an increase in intensityof the second contact above the respective intensity threshold; and inresponse to detecting the increase in intensity of the second contact,display a second animation of the second representation distorting inaccordance with the increase in intensity of the second contact.

In some embodiments, the first animation includes adjusting display ofthe first representation by displaying a plurality of visual cues inaccordance with the intensity of the first contact; and the secondanimation includes adjusting display of the second representation bydisplaying the plurality of visual cues in accordance with the intensityof the second contact.

The operations in the information processing methods described above areoptionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 18A-18E are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.19. For example, detection operation 8504, replacing operation 8508, andanimating operation 8532 are, optionally, implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 detects a contact on touch-sensitive display 112, andevent dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub-event,such as selection of an object on a user interface. When a respectivepredefined event or sub-event is detected, event recognizer 180activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 optionally utilizes or calls dataupdater 176 or object updater 177 to update the application internalstate 192. In some embodiments, event handler 190 accesses a respectiveGUI updater 178 to update what is displayed by the application.Similarly, it would be clear to a person having ordinary skill in theart how other processes can be implemented based on the componentsdepicted in FIGS. 1A-1B.

It should be understood that the particular order in which theoperations have been described above is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that the various processes separatelydescribed herein (e.g., those listed in the fifth paragraph of theDescription of Embodiments) can be combined with each other in differentarrangements. For example, the contacts, user interface objects, tactilesensations, intensity thresholds, and/or focus selectors described abovewith reference to any one of the various processes separately describedherein (e.g., those listed in the fifth paragraph of the Description ofEmbodiments) optionally have one or more of the characteristics of thecontacts, gestures, user interface objects, tactile sensations,intensity thresholds, and focus selectors described herein withreference to one or more of the other methods described herein (e.g.,those listed in the fifth paragraph of the Description of Embodiments).For brevity, all of the various possible combinations are notspecifically enumerated here, but it should be understood that theclaims described above may be combined in any way that is not precludedby mutually exclusive claim features.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the various described embodiments to the precise forms disclosed.Many modifications and variations are possible in view of the aboveteachings. The embodiments were chosen and described in order to bestexplain the principles of the various described embodiments and theirpractical applications, to thereby enable others skilled in the art tobest utilize the various described embodiments with variousmodifications as are suited to the particular use contemplated.

What is claimed is:
 1. A method, comprising: at an electronic devicewith a touch-sensitive surface and a display, wherein the deviceincludes one or more sensors to detect intensity of contacts with thetouch-sensitive surface: displaying a plurality of icons in a predefinedarea on the display, wherein the plurality of icons include a respectiveicon; detecting a gesture that includes: a contact on thetouch-sensitive surface while a focus selector is over the respectiveicon; and subsequent movement of the contact across the touch-sensitivesurface that corresponds to movement of the focus selector outside ofthe predefined area; and in response to detecting the gesture: inaccordance with a determination that the contact had a maximum intensityduring the gesture that was below a respective intensity threshold:displaying an indication that the gesture is being performed during thegesture; and retaining the respective icon in the predefined area afterthe gesture has ended; and in accordance with a determination that thecontact reached an intensity during the gesture that was above therespective intensity threshold: moving the respective icon in accordancewith the movement of the contact during the gesture; and removing therespective icon from the predefined area after the gesture has ended. 2.The method of claim 1, wherein displaying the indication that thegesture is being performed includes: changing an appearance of therespective icon in the predefined area; and while displaying therespective icon with the changed appearance on the display, moving arepresentation of the respective icon in accordance with movement of thecontact during the gesture.
 3. The method of claim 1, wherein displayingthe indication that the gesture is being performed includes, whilemaintaining the respective icon in a fixed location in the predefinedarea, moving a cursor on the display in accordance with movement of thecontact.
 4. The method of claim 1, wherein displaying the indicationthat the gesture is being performed includes, while constrainingmovement of the respective icon to the predefined area, moving therespective icon in accordance with the movement of the contact duringthe gesture.
 5. The method of claim 1, including: detecting a tapgesture on the touch-sensitive surface while the focus selector is overthe respective icon; and in response to detecting the tap gesture,launching a respective application associated with the respective icon.6. The method of claim 1, including, prior to detecting an end of thegesture: in accordance with a determination that the contact reached anintensity during the gesture that was above the respective intensitythreshold, prior to removing the respective icon from the predefinedarea, displaying a visual indication that the respective icon will beremoved from an application dock.
 7. An electronic device, comprising: adisplay; a touch-sensitive surface; one or more sensors to detectintensity of contacts with the touch-sensitive surface; one or moreprocessors; memory; and one or more programs, wherein the one or moreprograms are stored in the memory and configured to be executed by theone or more processors, the one or more programs including instructionsfor: displaying a plurality of icons in a predefined area on thedisplay, wherein the plurality of icons include a respective icon;detecting a gesture that includes: a contact on the touch-sensitivesurface while a focus selector is over the respective icon; andsubsequent movement of the contact across the touch-sensitive surfacethat corresponds to movement of the focus selector outside of thepredefined area; and in response to detecting the gesture: in accordancewith a determination that the contact had a maximum intensity during thegesture that was below a respective intensity threshold: displaying anindication that the gesture is being performed during the gesture; andretaining the respective icon in the predefined area after the gesturehas ended; and in accordance with a determination that the contactreached an intensity during the gesture that was above the respectiveintensity threshold: moving the respective icon in accordance with themovement of the contact during the gesture; and removing the respectiveicon from the predefined area after the gesture has ended.
 8. A computerreadable storage medium storing one or more programs, the one or moreprograms comprising instructions, which when executed by an electronicdevice with a display, a touch-sensitive surface, and one or moresensors to detect intensity of contacts with the touch-sensitivesurface, cause the device to: display a plurality of icons in apredefined area on the display, wherein the plurality of icons include arespective icon; detect a gesture that includes: a contact on thetouch-sensitive surface while a focus selector is over the respectiveicon; and subsequent movement of the contact across the touch-sensitivesurface that corresponds to movement of the focus selector outside ofthe predefined area; and in response to detecting the gesture: inaccordance with a determination that the contact had a maximum intensityduring the gesture that was below a respective intensity threshold:display an indication that the gesture is being performed during thegesture; and retain the respective icon in the predefined area after thegesture has ended; and in accordance with a determination that thecontact reached an intensity during the gesture that was above therespective intensity threshold: move the respective icon in accordancewith the movement of the contact during the gesture; and remove therespective icon from the predefined area after the gesture has ended.